Retrieves a specific application charge.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=
AI agents call retrieve_applications_charges to retrieve information from Wpm Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries existing charge data without modifying, deleting, or executing operations. No financial movement occurs; it only reads application charge information. Classified as Read with low severity due to minimal blast radius from misuse.
From the tool's definition Tool name 'retrieve_applications_charges' with verb 'retrieve' indicates data retrieval. Description explicitly states 'Retrieves a specific application charge' — a query operation with no side effects.
Attacks that exploit this kind of access
Retrieves a specific application charge.\r\n \r\n\r\n<h4>Required permission(s):</h4><span class=. It is categorised as a Read tool in the Wpm Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Wpm Mcp Server MCP server in PolicyLayer and add a rule for retrieve_applications_charges: 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 Wpm Mcp Server. Nothing to install.
retrieve_applications_charges 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 retrieve_applications_charges 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 retrieve_applications_charges. 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.
retrieve_applications_charges is provided by the Wpm Mcp Server MCP server (wpm-mcp-server-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 →