get_transaction
Get detailed information about a specific transaction.
This record as markdown: /tools/com-zype-mcp-server/get-transaction.md
What get_transaction does on Zype Com
AI agents call get_transaction to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
transaction_id | string | Yes | The transaction ID |
Parameters from the server's own tool schema.
Why get_transaction is rated Low
This tool queries and retrieves existing transaction details without creating, modifying, deleting, or executing any operations. It is a read-only operation with no side effects. The low severity reflects that financial data exposure is concerning but this tool itself does not move money, create obligations, or alter state.
From the tool's definition Tool name and description indicate retrieval of transaction data: 'Get detailed information about a specific transaction.' No modification, deletion, or execution is performed.
Attacks that exploit this kind of access
The rule that runs get_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_transaction, this is the rule to start with:
get_transaction is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Zype Com, apply this rule, and every get_transaction call is checked against it from then on.
Questions about get_transaction
Get detailed information about a specific transaction. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.
get_transaction accepts 1 parameter: transaction_id. Required: transaction_id. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for 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 Zype Com. Nothing to install.
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 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 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.
get_transaction is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
This server
Across the catalogue