get_transactions
AI agents call get_transactions to retrieve information from Sure MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix universally indicates data retrieval with no side effects. Financial data retrieval poses minimal risk compared to write/delete/execute operations on the same platform. A misused get_transactions call cannot alter state, delete data, or trigger external operations—it can only expose information the agent already has authorized access to query.
From the tool's definition Tool name 'get_transactions' combined with sibling tools 'get_accounts', 'get_categories', 'get_category', and 'get_chat' establishes a clear pattern of read-only retrieval operations.
Attacks that exploit this kind of access
get_transactions. It is categorised as a Read tool in the Sure MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sure MCP Server 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 Sure MCP Server. 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 Sure MCP Server MCP server (robcerda/sure-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_transactions is one line of Sure MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →