getTransactionStatus

Consulta o status de uma transação ZuckPay (PIX, SPEI ou cartão) pelo transactionId OU pelo external_id_client do seu sistema (exatamente um dos dois).

SERVERZuckpay SOURCEZuckPay/zuckpay-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/zuckpay-mcp/gettransactionstatus.md

WHAT IT DOES

What getTransactionStatus does on Zuckpay

AI agents call getTransactionStatus to retrieve information from Zuckpay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getTransactionStatus is rated Low

Even though getTransactionStatus only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getTransactionStatus safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zuckpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getTransactionStatus, this is the rule to start with:

getTransactionStatus Allowed

getTransactionStatus is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTransactionStatus": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zuckpay, apply this rule, and every getTransactionStatus call is checked against it from then on.

FAQ

Questions about getTransactionStatus

What does the getTransactionStatus tool do? +

Consulta o status de uma transação ZuckPay (PIX, SPEI ou cartão) pelo transactionId OU pelo external_id_client do seu sistema (exatamente um dos dois). It is categorised as a Read tool in the Zuckpay MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTransactionStatus? +

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

What risk level is getTransactionStatus? +

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

Can I rate-limit getTransactionStatus? +

Yes. Add a rate_limit block to the getTransactionStatus 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 getTransactionStatus completely? +

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

getTransactionStatus is provided by the Zuckpay MCP server (ZuckPay/zuckpay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zuckpay, and thousands of servers like it.

This server

All 9 Zuckpay tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →