AI agents call get_payment_method to retrieve information from Paymongo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries existing data (a payment method record) without creating, modifying, deleting, or executing operations. It has no financial impact and causes no side effects. It is classified as Read with low severity because exposure to an AI agent would only risk information disclosure of payment method details, not financial loss or destructive actions.
From the tool's definition Tool name 'get_payment_method' and description 'Retrieve a payment method by its ID' indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Retrieve a payment method by its ID. It is categorised as a Read tool in the Paymongo MCP Server, which means it retrieves data without modifying state.
Register the Paymongo MCP server in PolicyLayer and add a rule for get_payment_method: 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 Paymongo. Nothing to install.
get_payment_method 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 get_payment_method 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 get_payment_method. 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.
get_payment_method is provided by the Paymongo MCP server (theyahia/paymongo-mcp). 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 →