Low Risk

get_violent_incident_estimates

Get national estimates of violent crime incidents from NIBRS. Returns weighted national estimates of crimes against persons (violent crimes) including aggravated assault, homicide, kidnapping, robbery, and sex offenses. Data includes breakdowns by weapon, location type, victim-offender relationsh...

Part of the FBI NIBRS Crime Data server.

get_violent_incident_estimates is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE FBI NIBRS CRIME DATA →

Free to start. No card required.

AI agents call get_violent_incident_estimates to retrieve information from FBI NIBRS 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_violent_incident_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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_violent_incident_estimates": {}
  }
}

See the full FBI NIBRS Crime Data policy for all 4 tools.

Get this rule live on your own FBI NIBRS Crime Data server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FBI NIBRS CRIME DATA →

These attack patterns abuse exactly the kind of access get_violent_incident_estimates gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_violent_incident_estimates only ever does what you allow.

SECURE FBI NIBRS CRIME DATA →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_violent_incident_estimates tool do? +

Get national estimates of violent crime incidents from NIBRS. Returns weighted national estimates of crimes against persons (violent crimes) including aggravated assault, homicide, kidnapping, robbery, and sex offenses. Data includes breakdowns by weapon, location type, victim-offender relationship, and time of day. Args: indicator: Filter by offense type (e.g. 'Aggravated Assault', 'Robbery', 'NIBRS crimes against persons (Total)'). Omit for all offense types. domain: Filter by analysis domain. Options include: 'Incident count', 'Weapon involved', 'Location type', 'Victim-offender relationship', 'Time of day- Incident time', 'Multiple victims', 'Multiple offenders', 'Clearance', 'Injury', 'MSA', 'Population group'. Omit for all. limit: Maximum results to return (default 50, max 1000).. It is categorised as a Read tool in the FBI NIBRS Crime Data MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_violent_incident_estimates? +

Register the FBI NIBRS Crime Data MCP server in PolicyLayer and add a rule for get_violent_incident_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 NIBRS Crime Data. Nothing to install.

What risk level is get_violent_incident_estimates? +

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

Can I rate-limit get_violent_incident_estimates? +

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

How do I block get_violent_incident_estimates completely? +

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

What MCP server provides get_violent_incident_estimates? +

get_violent_incident_estimates is provided by the FBI NIBRS Crime Data MCP server (https://mcp.olyport.com/fbi-nibrs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FBI NIBRS Crime Data tool call.

Deterministic rules across all 4 FBI NIBRS 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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.