Get the status of a bridge transaction
AI agents call get_transaction_status to retrieve information from ValueRouter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves or queries the status of a bridge transaction. It has no side effects, does not execute any operations, does not modify data, and does not involve financial transactions themselves. It falls squarely into the Read category with low severity because misuse would only expose transaction information, not enable unauthorized financial movement or data modification.
From the tool's definition Tool name 'get_transaction_status' and description 'Get the status of a bridge transaction' indicate a query operation that retrieves information about an existing transaction without modifying or executing any operations.
Attacks that exploit this kind of access
Get the status of a bridge transaction. It is categorised as a Read tool in the ValueRouter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ValueRouter MCP Server MCP server in PolicyLayer and add a rule for get_transaction_status: 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 ValueRouter MCP Server. Nothing to install.
get_transaction_status 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_status 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_status. 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_status is provided by the ValueRouter MCP Server MCP server (rwavaluerouter/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 →