Valida assinatura HMAC do webhook (header X-OpenPix-Signature) usando sha1 e base64, conforme docs do OpenPix.
AI agents call woovi_verify_webhook_hmac to retrieve information from Payments MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a cryptographic verification function that checks the authenticity of incoming webhook data. It reads and validates a signature but does not create, modify, delete, or execute any operations. It does not move money or trigger external actions—it merely confirms the integrity of a webhook message.
From the tool's definition The tool 'woovi_verify_webhook_hmac' validates an HMAC signature from a webhook header (X-OpenPix-Signature) using sha1 and base64 encoding per OpenPix documentation.
Attacks that exploit this kind of access
Valida assinatura HMAC do webhook (header X-OpenPix-Signature) usando sha1 e base64, conforme docs do OpenPix. It is categorised as a Read tool in the Payments MCP MCP Server, which means it retrieves data without modifying state.
Register the Payments MCP server in PolicyLayer and add a rule for woovi_verify_webhook_hmac: 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 Payments MCP. Nothing to install.
woovi_verify_webhook_hmac 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 woovi_verify_webhook_hmac 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 woovi_verify_webhook_hmac. 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.
woovi_verify_webhook_hmac is provided by the Payments MCP server (lpillonwp/mcp-payments). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →