T09 · Insecure Skill Coding Practices
- Location
SKILL.md:543- Finding
Unauthenticated ACP Webhook Permits Forged Payment and Fulfillment Operations
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This non-executing guide is coherent, but its production-labeled payment and webhook examples could lead to insecure financial integrations if followed as-is.
Treat this as reference material only. Do not deploy the examples directly for real payments or public endpoints without adding strong request authentication, provider webhook signature verification, replay protection, authorization checks, explicit user payment approval, scoped credentials, webhook destination allowlisting, private-network egress blocking, and event-data minimization.
SKILL.md:543Unauthenticated ACP Webhook Permits Forged Payment and Fulfillment Operations
SKILL.md:2400Unrestricted Webhook Destinations Enable SSRF and Sensitive Event Exfiltration
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The 2026 agent protocol landscape has expanded from four major protocols to nine or more. The original four -- x402, ACP, A2A, and MCP -- have matured significantly into their v2 generations. x402 v2 is now backed by the x402 Foundation (Coinbase, Cloudflare, Stripe, AWS, and Microsoft) and has processed over 100 million payments. A2A v2 adds streaming-first task execution and enhanced Agent Card schemas. MCP 1.5+ introduces Streamable HTTP transport, resource subscriptions, and structured tool annotations. Meanwhile, five new heavyweight entrants have arrived: Visa's Transaction Authorization Protocol (TAP), Google's Agent Payments Protocol v2 (AP2) and Universal Commerce Protocol (UCP), PayPal's Agent Ready platform, and OpenAI's Agentic Commerce Protocol (OpenAI ACP). Each brings a different philosophy, a different merchant base, and a different set of integration requirements.
Every bridge class in this guide runs against the GreenHelix API at `https://api.greenhelix.net/v1`. Every code example is production-ready. By the end, your GreenHelix agents will accept x402 v2 micropayments, process ACP checkout flows, respond to A2A v2 task requests, expose services as MCP 1.5+ tools, authorize payments through Visa TAP, process Google AP2 payments and UCP task orchestration, integrate with PayPal's Agent Ready merchant network, and accept OpenAI ACP commerce flows -- without abandoning the escrow, identity, and trust infrastructure you have already built.
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The 2026 agent protocol landscape has expanded from four major protocols to nine or more. The original four -- x402, ACP, A2A, and MCP -- have matured significantly into their v2 generations. x402 v2 is now backed by the x402 Foundation (Coinbase, Cloudflare, Stripe, AWS, and Microsoft) and has processed over 100 million payments. A2A v2 adds streaming-first task execution and enhanced Agent Card schemas. MCP 1.5+ introduces Streamable HTTP transport, resource subscriptions, and structured tool annotations. Meanwhile, five new heavyweight entrants have arrived: Visa's Transaction Authorization Protocol (TAP), Google's Agent Payments Protocol v2 (AP2) and Universal Commerce Protocol (UCP), PayPal's Agent Ready platform, and OpenAI's Agentic Commerce Protocol (OpenAI ACP). Each brings a different philosophy, a different merchant base, and a different set of integration requirements.
Every bridge class in this guide runs against the GreenHelix API at `https://api.greenhelix.net/v1`. Every code example is production-ready. By the end, your GreenHelix agents will accept x402 v2 micropayments, process ACP checkout flows, respond to A2A v2 task requests, expose services as MCP 1.5+ tools, authorize payments through Visa TAP, process Google AP2 payments and UCP task orchestration, integrate with PayPal's Agent Ready merchant network, and accept OpenAI ACP commerce flows -- without abandoning the escrow, identity, and trust infrastructure you have already built.
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The 2026 agent protocol landscape has expanded from four major protocols to nine or more. The original four -- x402, ACP, A2A, and MCP -- have matured significantly into their v2 generations. x402 v2 is now backed by the x402 Foundation (Coinbase, Cloudflare, Stripe, AWS, and Microsoft) and has processed over 100 million payments. A2A v2 adds streaming-first task execution and enhanced Agent Card schemas. MCP 1.5+ introduces Streamable HTTP transport, resource subscriptions, and structured tool annotations. Meanwhile, five new heavyweight entrants have arrived: Visa's Transaction Authorization Protocol (TAP), Google's Agent Payments Protocol v2 (AP2) and Universal Commerce Protocol (UCP), PayPal's Agent Ready platform, and OpenAI's Agentic Commerce Protocol (OpenAI ACP). Each brings a different philosophy, a different merchant base, and a different set of integration requirements.
Every bridge class in this guide runs against the GreenHelix API at `https://api.greenhelix.net/v1`. Every code example is production-ready. By the end, your GreenHelix agents will accept x402 v2 micropayments, process ACP checkout flows, respond to A2A v2 task requests, expose services as MCP 1.5+ tools, authorize payments through Visa TAP, process Google AP2 payments and UCP task orchestration, integrate with PayPal's Agent Ready merchant network, and accept OpenAI ACP commerce flows -- without abandoning the escrow, identity, and trust infrastructure you have already built.
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The 2026 agent protocol landscape has expanded from four major protocols to nine or more. The original four -- x402, ACP, A2A, and MCP -- have matured significantly into their v2 generations. x402 v2 is now backed by the x402 Foundation (Coinbase, Cloudflare, Stripe, AWS, and Microsoft) and has processed over 100 million payments. A2A v2 adds streaming-first task execution and enhanced Agent Card schemas. MCP 1.5+ introduces Streamable HTTP transport, resource subscriptions, and structured tool annotations. Meanwhile, five new heavyweight entrants have arrived: Visa's Transaction Authorization Protocol (TAP), Google's Agent Payments Protocol v2 (AP2) and Universal Commerce Protocol (UCP), PayPal's Agent Ready platform, and OpenAI's Agentic Commerce Protocol (OpenAI ACP). Each brings a different philosophy, a different merchant base, and a different set of integration requirements.
Every bridge class in this guide runs against the GreenHelix API at `https://api.greenhelix.net/v1`. Every code example is production-ready. By the end, your GreenHelix agents will accept x402 v2 micropayments, process ACP checkout flows, respond to A2A v2 task requests, expose services as MCP 1.5+ tools, authorize payments through Visa TAP, process Google AP2 payments and UCP task orchestration, integrate with PayPal's Agent Ready merchant network, and accept OpenAI ACP commerce flows -- without abandoning the escrow, identity, and trust infrastructure you have already built.
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
The 2026 agent protocol landscape has expanded from four major protocols to nine or more. The original four -- x402, ACP, A2A, and MCP -- have matured significantly into their v2 generations. x402 v2 is now backed by the x402 Foundation (Coinbase, Cloudflare, Stripe, AWS, and Microsoft) and has processed over 100 million payments. A2A v2 adds streaming-first task execution and enhanced Agent Card schemas. MCP 1.5+ introduces Streamable HTTP transport, resource subscriptions, and structured tool annotations. Meanwhile, five new heavyweight entrants have arrived: Visa's Transaction Authorization Protocol (TAP), Google's Agent Payments Protocol v2 (AP2) and Universal Commerce Protocol (UCP), PayPal's Agent Ready platform, and OpenAI's Agentic Commerce Protocol (OpenAI ACP). Each brings a different philosophy, a different merchant base, and a different set of integration requirements.
Every bridge class in this guide runs against the GreenHelix API at `https://api.greenhelix.net/v1`. Every code example is production-ready. By the end, your GreenHelix agents will accept x402 v2 micropayments, process ACP checkout flows, respond to A2A v2 task requests, expose services as MCP 1.5+ tools, authorize payments through Visa TAP, process Google AP2 payments and UCP task orchestration, integrate with PayPal's Agent Ready merchant network, and accept OpenAI ACP commerce flows -- without abandoning the escrow, identity, and trust infrastructure you have already built.
---
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
raise ValueError("Payment proof missing required fields")
# Verify with the facilitator that the payment settled
verify_resp = requests.post(
f"{self.facilitator_url}/verify",
json={
"tx_hash": tx_hash,
The guide states that simpler MCP clients may ignore the payment field and that payment can settle 'in the background,' which normalizes charging behavior without explicit user confirmation. In an agent-tool ecosystem, this can lead to unintended or opaque charges, especially when callers do not understand that tool use may incur real payment obligations.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
}
# Submit to acquiring bank
auth_response = requests.post(
f"{self.acquiring_bank_endpoint}/authorize",
json=auth_request,
cert=self.tap_certificate_path,
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Checks token format, expiry, and whether the token is on the
network's revocation list.
"""
validation_resp = requests.post(
f"{self.acquiring_bank_endpoint}/validate-token",
json={"token": tap_token},
cert=self.tap_certificate_path,
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
},
}
bt_response = requests.post(
self._bt_base_url,
json={"query": mutation, "variables": variables},
auth=(self.braintree_api_key, self.braintree_api_secret),
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
},
}
bt_response = requests.post(
self._bt_base_url,
json={"query": mutation, "variables": variables},
auth=(self.braintree_api_key, self.braintree_api_secret),
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
def __init__(self, client: GreenHelixClient, agent_id: str,
openai_acp_api_key: str,
openai_acp_base_url: str = "https://api.openai.com/v1/acp"):
self.client = client
self.agent_id = agent_id
self.openai_acp_api_key = openai_acp_api_key
The EventBridge forwards translated events to arbitrary registered webhook URLs using requests.post, creating server-side outbound requests based on stored URL input. Without strict allowlisting and validation, this can enable SSRF, internal network access, or sensitive event exfiltration to attacker-controlled endpoints.
continue
try:
resp = requests.post(
webhook["url"],
json=translated,
timeout=10,
The ACP webhook example processes incoming events directly from request JSON without verifying the Stripe webhook signature, even though the guide later says signature verification is required. An attacker could forge checkout or payment-completed events and trigger fulfillment logic or internal state changes without a legitimate Stripe-confirmed payment.
The A2A task endpoint example accepts unauthenticated POST requests and immediately translates them into service and payment-intent actions, despite the guide stating that push/webhook notifications should be authenticated. This allows unauthorized callers to submit fake tasks, consume resources, and potentially create bogus payment or event records.
The MCP endpoint executes tools based only on a JSON-RPC request plus an optional X-AGENT-ID header, while the guide claims paid tools should use OAuth 2.1 and balance checks. An attacker can spoof caller identity, invoke paid or state-changing tools, and cause unauthorized actions or charges because there is no real authentication, authorization, or payment enforcement in the example.
L2766 instructs implementers to validate Braintree webhook signatures before processing settlement events. The surrounding PayPal bridge examples include payment processing and token validation logic but omit any signature-validation step for incoming webhooks, creating a contradiction between the guide's security instructions and its implementation examples.