Get transaction details by order number
AI agents call get_transaction_by_order 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 transaction details based on an order number query parameter. It performs a read-only lookup of existing data without creating, modifying, deleting, or executing any operations. While it accesses financial transaction data, the tool itself is read-only and poses minimal risk if misused by an AI agent—it can only expose information, not move money or alter state.
From the tool's definition Tool name is 'get_transaction_by_order' and description states 'Get transaction details by order number' — this is a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get transaction details by order number. 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_transaction_by_order: 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_transaction_by_order 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_transaction_by_order 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_transaction_by_order. 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_transaction_by_order 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 →