AI agents call mono_health to retrieve information from Monospay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only health/status check operation. It retrieves the operational state of the payment gateway without modifying any data, executing code, making financial transactions, or destroying anything. The worst-case misuse would be to spam health checks, which would be a low-severity DoS concern, but the tool itself is fundamentally a Read operation.
From the tool's definition Tool name 'mono_health' and description 'Check if the mono payment gateway is online and healthy' indicate a status check operation with no data modification or financial transaction.
Attacks that exploit this kind of access
Check if the mono payment gateway is online and healthy. It is categorised as a Read tool in the Monospay MCP Server, which means it retrieves data without modifying state.
Register the Monospay MCP server in PolicyLayer and add a rule for mono_health: 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 Monospay. Nothing to install.
mono_health 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 mono_health 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 mono_health. 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.
mono_health is provided by the Monospay MCP server (monospay/monospay). 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 →