Get detailed status and info for a specific payment ID.
AI agents call get_payment to retrieve information from PayArk MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns information about an existing payment; it does not create, modify, delete, or execute financial operations. It is purely informational. While it accesses financial data (which could be sensitive), the tool itself performs no irreversible actions, executes no code, and commits no financial obligations.
From the tool's definition Tool name 'get_payment' and description 'Get detailed status and info for a specific payment ID' indicate a retrieval operation with no modification, deletion, or financial transaction capability.
Attacks that exploit this kind of access
Get detailed status and info for a specific payment ID. It is categorised as a Read tool in the PayArk MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PayArk MCP Server MCP server in PolicyLayer and add a rule for get_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 PayArk MCP Server. Nothing to install.
get_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 get_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 get_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.
get_payment is provided by the PayArk MCP Server MCP server (payark-inc/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 →