Get FBI crime estimates for a US state over a range of years. Returns annual crime estimate data from the FBI Crime Data Explorer for the specified state and crime category. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'NY'). crime_type: Type of crime to query. Options: violent...
Part of the FBI Crime Data server.
Free to start. No card required.
AI agents call get_state_crime_estimates to retrieve information from FBI Crime Data 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_state_crime_estimates 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_state_crime_estimates": {}
}
}See the full FBI Crime Data policy for all 4 tools.
These attack patterns abuse exactly the kind of access get_state_crime_estimates 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.
Get FBI crime estimates for a US state over a range of years. Returns annual crime estimate data from the FBI Crime Data Explorer for the specified state and crime category. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'NY'). crime_type: Type of crime to query. Options: violent-crime, property-crime, burglary, larceny, motor-vehicle-theft, homicide, robbery, aggravated-assault. Default: violent-crime. from_year: Start year for the data range (default 2015). to_year: End year for the data range (default 2023).. It is categorised as a Read tool in the FBI Crime Data MCP Server, which means it retrieves data without modifying state.
Register the FBI Crime Data MCP server in PolicyLayer and add a rule for get_state_crime_estimates: 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 FBI Crime Data. Nothing to install.
get_state_crime_estimates 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_state_crime_estimates 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_state_crime_estimates. 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_state_crime_estimates is provided by the FBI Crime Data MCP server (https://mcp.olyport.com/fbi-crime/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 FBI Crime Data 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.