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 Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a cryptographic validation function that verifies webhook authenticity by comparing signatures. It retrieves or confirms the validity of incoming data without creating, modifying, deleting, or executing operations. The tool only performs read-like operations (signature comparison) to determine if an event is legitimate.
From the tool's definition Tool description specifies 'Validate a Wompi event signature' using cryptographic verification (SHA-256 checksum or HMAC-SHA256). The verb 'validate' indicates a query/verification operation that checks credentials against a secret without modifying data.
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 Afip, 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 Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip 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 Afip. 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 Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, 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 Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.