fetch_payment_links
AI agents call fetch_payment_links to retrieve information from Paytm MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves payment link data without modifying or deleting anything. It is categorized as Read. Severity is high (not critical) because payment link information could expose sensitive transaction metadata, user details, or payment history if exfiltrated by a compromised agent, but the tool itself performs no financial transactions or destructive actions.
From the tool's definition Tool name 'fetch_payment_links' indicates a retrieval operation. Server context describes it as part of functionality to 'list created links' and 'retrieve transaction details'.
Attacks that exploit this kind of access
fetch_payment_links. It is categorised as a Read tool in the Paytm MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Paytm MCP Server MCP server in PolicyLayer and add a rule for fetch_payment_links: 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 Paytm MCP Server. Nothing to install.
fetch_payment_links 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 fetch_payment_links 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 fetch_payment_links. 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.
fetch_payment_links is provided by the Paytm MCP Server MCP server (shivam3-garg/payment-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 →