AI agents call list_webhook_alerts to retrieve information from Moneroo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns alert rules from a configuration file. It performs a read-only operation with no side effects, no data modification, and no execution of external operations. The severity is low because alert rule metadata has limited sensitivity compared to financial or transaction data, though exposure of alert configuration could inform an attacker about monitoring practices.
From the tool's definition Tool name is 'list_webhook_alerts' and description states 'List all saved alert rules from ~/.moneroo-mcp/alerts.json.' The verb 'List' indicates data retrieval without modification or side effects.
Attacks that exploit this kind of access
List all saved alert rules from ~/.moneroo-mcp/alerts.json. It is categorised as a Read tool in the Moneroo MCP Server, which means it retrieves data without modifying state.
Register the Moneroo MCP server in PolicyLayer and add a rule for list_webhook_alerts: 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 Moneroo. Nothing to install.
list_webhook_alerts 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 list_webhook_alerts 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 list_webhook_alerts. 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.
list_webhook_alerts is provided by the Moneroo MCP server (moneroo-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 →