AI agents call get_transactions to retrieve information from JoeMCP 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 financial transaction data with optional filtering by date range. It performs no side effects, does not move money, does not execute operations, and does not modify or delete data. It is a straightforward read operation that falls under the Read category.
From the tool's definition Tool name 'get_transactions' and description 'Get transaction list for a project with optional date range filtering' indicate a retrieval operation with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get transaction list for a project with optional date range filtering. It is categorised as a Read tool in the JoeMCP MCP Server, which means it retrieves data without modifying state.
Register the Joe MCP server in PolicyLayer and add a rule for get_transactions: 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 JoeMCP. Nothing to install.
get_transactions 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_transactions 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_transactions. 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_transactions is provided by the Joe MCP server (lumberjack-so/joemcp). 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 →