Get full details for a specific transaction. Returns comprehensive information including attachments, splits, tags, and more. Args: transaction_id: The ID of the transaction to get details for Returns: Complete transaction details.
AI agents call get_transaction_details to retrieve information from Monarch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and returns transaction information without any side effects. It takes a transaction_id as input and returns data only. This matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because retrieving transaction details poses minimal risk—it exposes data the user already has access to within their Monarch Money account,…
From the tool's definition Tool description states 'Get full details for a specific transaction' and 'Returns comprehensive information including attachments, splits, tags, and more.' This is a query/retrieval operation with no modification, deletion, or execution of external commands.
Documented attack patterns abuse exactly the kind of access get_transaction_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Monarch, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transaction_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_transaction_details": {}
}
}get_transaction_details 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 full details for a specific transaction. Returns comprehensive information including attachments, splits, tags, and more. Args: transaction_id: The ID of the transaction to get details for Returns: Complete transaction details. It is categorised as a Read tool in the Monarch MCP Server, which means it retrieves data without modifying state.
Register the Monarch MCP server in PolicyLayer and add a rule for get_transaction_details: 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 Monarch. Nothing to install.
get_transaction_details 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_details 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_details. 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_details is provided by the Monarch MCP server (robcerda/monarch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 Monarch tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 Monarch tools catalogued and risk-classified — across an index of 42,500+ MCP servers.