get_city_alerts

Get alert history for a specific city from the local SQLite database.

Server Pikud Haoref Alert System leonmelamud/pikud-a-oref-mcp
Category Read
Risk class Low
Parameters 00 required

What get_city_alerts does on Pikud Haoref Alert System

AI agents call get_city_alerts 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.

Why get_city_alerts needs a policy

This tool queries historical alert data filtered by city. It retrieves information without creating, modifying, deleting, or executing operations with side effects. The blast radius of misuse is minimal — worst case an agent repeatedly queries the database for information it already has access to. No irreversible changes, code execution, or financial impact is possible.

From the tool's definition Tool description states 'Get alert history for a specific city from the local SQLite database' — this is a retrieval operation with no modification or deletion of data. The verb 'Get' and the phrase 'from the local SQLite database' indicate a read-only query.

Questions about get_city_alerts

What does the get_city_alerts tool do? +

Get alert history for a specific city from the local SQLite database. It is categorised as a Read tool in the Pikud Haoref Alert System MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_city_alerts? +

Register the Pikud Haoref Alert System MCP server in PolicyLayer and add a rule for get_city_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 Pikud Haoref Alert System. Nothing to install.

What risk level is get_city_alerts? +

get_city_alerts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_city_alerts? +

Yes. Add a rate_limit block to the get_city_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.

How do I block get_city_alerts completely? +

Set action: deny in the PolicyLayer policy for get_city_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.

What MCP server provides get_city_alerts? +

get_city_alerts 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.