AI agents call get_disbursement to retrieve information from Xendit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves disbursement details by querying an ID. It has no side effects—it does not create, modify, delete, or execute operations. It is a straightforward read operation similar to other retrieval tools on the server (get_balance, get_invoice, get_va_payment, list_invoices). The severity is low because misuse would only expose information about a disbursement, not cause financial transactions or data loss.
From the tool's definition Tool name 'get_disbursement' and description 'Get disbursement details by ID' indicate a read-only operation that retrieves existing disbursement information without modifying or deleting data.
Attacks that exploit this kind of access
Get disbursement details by ID. It is categorised as a Read tool in the Xendit MCP Server, which means it retrieves data without modifying state.
Register the Xendit MCP server in PolicyLayer and add a rule for get_disbursement: 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 Xendit. Nothing to install.
get_disbursement 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_disbursement 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_disbursement. 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_disbursement is provided by the Xendit MCP server (theyahia/xendit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →