Get statistics about the local alert database.
AI agents call get_db_stats to retrieve information from Pikud Haoref Alert System without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database statistics, which is a read operation with no side effects. It does not modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only retrieve statistical metadata about the alert database, which poses no risk to data integrity or external systems.
From the tool's definition Tool name 'get_db_stats' and description 'Get statistics about the local alert database' indicate retrieval of database statistics without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get statistics about the local alert database. It is categorised as a Read tool in the Pikud Haoref Alert System MCP Server, which means it retrieves data without modifying state.
Register the Pikud Haoref Alert System MCP server in PolicyLayer and add a rule for get_db_stats: 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 Pikud Haoref Alert System. Nothing to install.
get_db_stats 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 get_db_stats 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 get_db_stats. 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.
get_db_stats is provided by the Pikud Haoref Alert System MCP server (leonmelamud/pikud-a-oref-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 →