Check multiple price alerts at once
AI agents call check_multiple_alerts to retrieve information from Crypto Portfolio MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing price alert configurations and their current states across the portfolio without creating, modifying, deleting, or executing any operations. It is a passive data retrieval operation with no side effects, fitting squarely within the Read category. The read-only nature of the server and the passive verb 'check' confirm low severity.
From the tool's definition Tool name 'check_multiple_alerts' and description 'Check multiple price alerts at once' indicate retrieval of alert status data. Server is explicitly described as 'read-only portfolio management and analytics'.
Attacks that exploit this kind of access
Check multiple price alerts at once. It is categorised as a Read tool in the Crypto Portfolio MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Crypto Portfolio MCP Server MCP server in PolicyLayer and add a rule for check_multiple_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 Crypto Portfolio MCP Server. Nothing to install.
check_multiple_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 check_multiple_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 check_multiple_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.
check_multiple_alerts is provided by the Crypto Portfolio MCP Server MCP server (lev-corrupted/cryptoportfoliomcpserver). 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 →