Returns prioritized, time-critical emergency action steps for active water or fire damage in Philadelphia. Includes safety warnings, step-by-step instructions with time sensitivity flags, Philadelphia emergency contacts (PWD, PECO, PGW, Philadelphia Fire Department), and documentation checklist f...
Part of the Philadelphia Restoration server.
Free to start. No card required.
AI agents call get_emergency_steps to retrieve information from Philadelphia Restoration without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_emergency_steps only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_emergency_steps": {}
}
}See the full Philadelphia Restoration policy for all 7 tools.
These attack patterns abuse exactly the kind of access get_emergency_steps gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Returns prioritized, time-critical emergency action steps for active water or fire damage in Philadelphia. Includes safety warnings, step-by-step instructions with time sensitivity flags, Philadelphia emergency contacts (PWD, PECO, PGW, Philadelphia Fire Department), and documentation checklist for insurance claims. Use this tool FIRST when a homeowner has an active emergency.. It is categorised as a Read tool in the Philadelphia Restoration MCP Server, which means it retrieves data without modifying state.
Register the Philadelphia Restoration MCP server in PolicyLayer and add a rule for get_emergency_steps: 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 Philadelphia Restoration. Nothing to install.
get_emergency_steps 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_emergency_steps 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_emergency_steps. 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_emergency_steps is provided by the Philadelphia Restoration MCP server (https://mcp.philadelphiarestoration.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Philadelphia Restoration tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.