fbi.crime.national_annual
Retrieve national year-over-year annual crime totals from FBI UCR data, aggregated from monthly reporting. Returns total offense counts, average rate per 100,000 population, total clearances, and clearance rate percentage for each calendar year. Supports date ranges spanning multiple decades (dat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fbi.crime.national-annual.md
What fbi.crime.national_annual does on Apibase
AI agents call fbi.crime.national_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.national_annual is rated Low
Tool queries public FBI crime statistics with no write, delete, execute, or financial capabilities.
From the tool's definition Retrieve national year-over-year annual crime totals from FBI UCR data
Attacks that exploit this kind of access
The rule that runs fbi.crime.national_annual safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fbi.crime.national_annual, this is the rule to start with:
fbi.crime.national_annual is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every fbi.crime.national_annual call is checked against it from then on.
Questions about fbi.crime.national_annual
Retrieve national year-over-year annual crime totals from FBI UCR data, aggregated from monthly reporting. Returns total offense counts, average rate per 100,000 population, total clearances, and clearance rate percentage for each calendar year. Supports date ranges spanning multiple decades (data available from 1979). Ideal for long-term trend analysis: "Has the US murder rate declined since the 1990s?" or "What are 10-year property crime trends?". 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.
fbi.crime.national_annual accepts 3 parameters: to_year, from_year, offense_type. Required: offense_type. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for fbi.crime.national_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.
fbi.crime.national_annual 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 fbi.crime.national_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.
Set action: deny in the PolicyLayer policy for fbi.crime.national_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.
fbi.crime.national_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.
This server
Across the catalogue