Low Risk

get_transaction_detail

Retrieve a stored transaction by transaction ID

How to control get_transaction_detail ↓

What get_transaction_detail does on Mcp Ap2

AI agents call get_transaction_detail to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_transaction_detail needs a policy

This tool retrieves transaction information from storage without modifying, deleting, or executing any financial operations. While it accesses financial data, the act of retrieval alone is a Read operation. The low severity reflects that viewing transaction details poses minimal direct risk unless the data itself is highly sensitive, but the tool performs no financial transfers, authorizations, or state changes.

From the tool's definition Tool name 'get_transaction_detail' and description 'Retrieve a stored transaction by transaction ID' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_transaction_detail gives an agent:

How to control get_transaction_detail

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_transaction_detail:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_transaction_detail": {}
  }
}

get_transaction_detail is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_transaction_detail

What does the get_transaction_detail tool do? +

Retrieve a stored transaction by transaction ID. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_transaction_detail? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for get_transaction_detail: 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 Mcp Ap2. Nothing to install.

What risk level is get_transaction_detail? +

get_transaction_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_transaction_detail? +

Yes. Add a rate_limit block to the get_transaction_detail 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.

How do I block get_transaction_detail completely? +

Set action: deny in the PolicyLayer policy for get_transaction_detail. 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.

What MCP server provides get_transaction_detail? +

get_transaction_detail is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.