search_shelters

THE RISK

Low Risk

Why search_shelters needs a policy

This tool queries and retrieves shelter location data based on geographic coordinates or city names. It performs a search/lookup operation with no capability to modify, create, delete, or execute operations. The blast radius of misuse is minimal—worst case would be returning irrelevant or excessive shelter results. This is a straightforward Read operation.

From the tool's definition Tool description states 'Find nearby shelters' with search functionality based on location input. No modification, deletion, or execution of external systems indicated. Returns shelter location data without side effects.

Documented attack patterns abuse exactly the kind of access search_shelters gives an agent:

POLICY

How to control search_shelters

PolicyLayer is an MCP gateway — it sits between your AI agents and RedAlert MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_shelters:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_shelters": {}
  }
}

search_shelters is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register RedAlert MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More RedAlert MCP Server tools

Execute subscribe_alerts Connect to RedAlert Socket.IO server and start receiving real-time emergency alerts. Optio Write unsubscribe_alerts Disconnect from RedAlert Socket.IO server and stop receiving real-time alerts. Clears the Read get_active_alerts Get real-time snapshot of cities currently under alert, grouped by alert type (missiles, e Read get_alert_subscription_status Check the current real-time alert subscription status including connection state, subscrib Read get_cities Get city catalog for lookups - raw location records with optional translations, coordinate Read get_stats_cities Get city-level alert statistics with pagination, search, and optional translations/coordin Read get_stats_distribution Get alert distribution grouped by category or origin, with filtering, sorting, and paginat Read get_stats_history Get detailed historical alert records with full city data, filtering, sorting, and paginat

All 12 RedAlert MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_shelters

What does the search_shelters tool do? +

Find nearby shelters. Provide lat/lon directly, or just a city name to auto-resolve coordinates. It is categorised as a Read tool in the RedAlert MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_shelters? +

Register the RedAlert MCP Server MCP server in PolicyLayer and add a rule for search_shelters: 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 RedAlert MCP Server. Nothing to install.

What risk level is search_shelters? +

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

Can I rate-limit search_shelters? +

Yes. Add a rate_limit block to the search_shelters 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 search_shelters completely? +

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

search_shelters is provided by the RedAlert MCP Server MCP server (ozba/redalert-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RedAlert MCP Server tool call.

Start from RedAlert MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →