New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

fbi.crime.state_annual

Retrieve state-level annual crime totals from FBI UCR data with national comparison, aggregated from monthly reporting. Returns year-by-year offense counts, rates, clearances, and clearance rates for both the specified state and the national average. Perfect for tracking state crime trends over t...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fbi.crime.state-annual.md

What fbi.crime.state_annual does on Apibase

AI agents call fbi.crime.state_annual to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
state string Yes Two-letter US state abbreviation (e.g. CA, TX, NY, FL). All 50 states + DC supported.
to_year integer — End year for annual trend data inclusive (e.g. 2022). Defaults to last full year.
from_year integer — Start year for annual trend data (e.g. 2010). Data available from 1979.
offense_type string Yes FBI UCR offense category. violent-crime (murder+rape+robbery+assault), property-crime (burglary+larceny+auto+arson), or individual offense type

Parameters from the server's own tool schema.

Why fbi.crime.state_annual is rated Low

Fetches public FBI crime statistics without modification or execution capabilities.

From the tool's definition Retrieve state-level annual crime totals from FBI UCR data with national comparison.

Questions about fbi.crime.state_annual

What does the fbi.crime.state_annual tool do? +

Retrieve state-level annual crime totals from FBI UCR data with national comparison, aggregated from monthly reporting. Returns year-by-year offense counts, rates, clearances, and clearance rates for both the specified state and the national average. Perfect for tracking state crime trends over time and comparing against the national picture. Supports 50 states + DC (2-letter code) and multi-decade date ranges back to 1979. Source: FBI UCR / CDE, US Gov public domain, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does fbi.crime.state_annual accept? +

fbi.crime.state_annual accepts 4 parameters: state, to_year, from_year, offense_type. Required: state, offense_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fbi.crime.state_annual? +

Register the Apibase MCP server in PolicyLayer and add a rule for fbi.crime.state_annual: 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 Apibase. Nothing to install.

What risk level is fbi.crime.state_annual? +

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

Can I rate-limit fbi.crime.state_annual? +

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

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

fbi.crime.state_annual is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Apibase, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

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.