Get detailed information about a specific transaction by ID
AI agents call crow_actual_get_transaction to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries transaction data by ID and returns information without altering, deleting, or executing operations. It is a standard read operation. Severity is low because retrieving transaction details poses minimal risk; the tool does not move money, modify records, or execute external actions.
From the tool's definition Tool name includes 'get' and description states 'Get detailed information about a specific transaction by ID'—a retrieval operation with no modification.
Documented attack patterns abuse exactly the kind of access crow_actual_get_transaction gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_actual_get_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"crow_actual_get_transaction": {}
}
} crow_actual_get_transaction 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.
Get detailed information about a specific transaction by ID. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_actual_get_transaction: 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 Crow. Nothing to install.
crow_actual_get_transaction 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 crow_actual_get_transaction 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 crow_actual_get_transaction. 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.
crow_actual_get_transaction is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.