Get payment intent details and status by payment intent ID. Returns comprehensive payment history including all attempts.
AI agents call get_payment_intent to retrieve information from Bayarcash 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 and queries payment intent information by ID. It reads payment history and status without creating, modifying, deleting, or executing transactions. The operation is purely informational with no blast radius if misused — an AI agent querying payment intents cannot cause financial harm, data loss, or unintended state changes.
From the tool's definition Tool name contains 'get' and description states 'Get payment intent details and status' and 'Returns comprehensive payment history' — these are data retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
Get payment intent details and status by payment intent ID. Returns comprehensive payment history including all attempts. It is categorised as a Read tool in the Bayarcash MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bayarcash MCP Server MCP server in PolicyLayer and add a rule for get_payment_intent: 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 Bayarcash MCP Server. Nothing to install.
get_payment_intent 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_intent 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_intent. 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_intent is provided by the Bayarcash MCP Server MCP server (webimpianteam/bayarcash-mcp-server). 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 →