Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID.
AI agents call lookup_payment to retrieve information from PayRam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries payment data based on provided identifiers. It has no side effects—it does not create, modify, delete, or execute operations. While it accesses potentially sensitive payment information, the risk is limited to information disclosure rather than active manipulation or financial movement. This is a standard Read operation.
From the tool's definition Tool name 'lookup_payment' and description 'Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID' indicate a query/retrieval operation with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access lookup_payment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PayRam MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lookup_payment:
{
"version": "1",
"default": "deny",
"tools": {
"lookup_payment": {}
}
}lookup_payment 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.
Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID. It is categorised as a Read tool in the PayRam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PayRam MCP Server MCP server in PolicyLayer and add a rule for lookup_payment: 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 PayRam MCP Server. Nothing to install.
lookup_payment 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 lookup_payment 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 lookup_payment. 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.
lookup_payment is provided by the PayRam MCP Server MCP server (payram/payram-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 35 PayRam MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
35 PayRam MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.