midtrans_get_charge_example
AI agents call midtrans_get_charge_example to retrieve information from MCP Midtrans Documentation Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or provide example charge request code/documentation without executing transactions or making actual API calls that would move money or modify payment state. It functions as a documentation/reference tool similar to its siblings. The 'get' verb and lack of parameters suggesting actual transaction execution indicate read-only behavior.
From the tool's definition Tool name 'midtrans_get_charge_example' and context within a documentation server suggest it retrieves or fetches example code/documentation for charge requests.
Attacks that exploit this kind of access
midtrans_get_charge_example. It is categorised as a Read tool in the MCP Midtrans Documentation Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Midtrans Documentation Server MCP server in PolicyLayer and add a rule for midtrans_get_charge_example: 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 Midtrans Documentation Server. Nothing to install.
midtrans_get_charge_example 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 midtrans_get_charge_example 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 midtrans_get_charge_example. 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.
midtrans_get_charge_example is provided by the MCP Midtrans Documentation Server MCP server (rissets/mcp-midtrans). 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 →