Validate a Wompi event signature. Accepts either the properties-based checksum (SHA-256 of ordered props + timestamp + WOMPI_EVENTS_SECRET) or a raw-body HMAC-SHA256 signature.
AI agents call validate_webhook_signature to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs cryptographic verification only. It reads and authenticates data without side effects, matching the Read category definition. While signature validation is security-sensitive, the tool itself does not modify, execute commands, delete data, or commit financial obligations. Misuse (e.g., accepting forged webhooks if validation is bypassed) would be downstream, not intrinsic to this tool.
From the tool's definition validate_webhook_signature — validates/verifies an incoming webhook signature by comparing checksums or HMAC-SHA256 signatures against expected values. No state is modified, created, deleted, or financial transaction is initiated.
Documented attack patterns abuse exactly the kind of access validate_webhook_signature gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_webhook_signature:
{
"version": "1",
"default": "deny",
"tools": {
"validate_webhook_signature": {}
}
}validate_webhook_signature is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Validate a Wompi event signature. Accepts either the properties-based checksum (SHA-256 of ordered props + timestamp + WOMPI_EVENTS_SECRET) or a raw-body HMAC-SHA256 signature. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for validate_webhook_signature: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Ap2. Nothing to install.
validate_webhook_signature is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the validate_webhook_signature rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for validate_webhook_signature. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
validate_webhook_signature is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.