fbi_cde_state_crime_trend
Return a bounded monthly trend for one state and one FBI summarized UCR offense category from LiveDataLink's self-hosted official CDE aggregate snapshot. Fields include reported offenses and clearances, rates per 100,000 reporting population, full and reporting populations, coverage percentage, p...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fbi-cde-state-crime-trend.md
What fbi_cde_state_crime_trend does on Livedatalink
AI agents call fbi_cde_state_crime_trend to retrieve information from Livedatalink 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 |
|---|---|---|---|
limit | integer | — | Maximum monthly observations. Default 24. |
state | string | Yes | Two-letter U.S. state or District of Columbia abbreviation; US is not accepted. |
offset | integer | — | Monthly observations to skip. Default 0. |
offense | string | Yes | FBI CDE summarized offense category. Aggregate categories overlap their component offenses. |
end_month | string | Yes | Calendar month in YYYY-MM format within the hosted snapshot. |
start_month | string | Yes | Calendar month in YYYY-MM format within the hosted snapshot. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why fbi_cde_state_crime_trend is rated Low
Even though fbi_cde_state_crime_trend only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs fbi_cde_state_crime_trend safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fbi_cde_state_crime_trend, this is the rule to start with:
fbi_cde_state_crime_trend 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 Livedatalink, apply this rule, and every fbi_cde_state_crime_trend call is checked against it from then on.
Questions about fbi_cde_state_crime_trend
Return a bounded monthly trend for one state and one FBI summarized UCR offense category from LiveDataLink's self-hosted official CDE aggregate snapshot. Fields include reported offenses and clearances, rates per 100,000 reporting population, full and reporting populations, coverage percentage, pagination, and exact provenance. Use this for 'California violent-crime trend in 2023', 'monthly motor vehicle theft reported in Texas', or 'did coverage change during this state trend?'. Crimes known to law enforcement only; never use for cross-state rankings or individual decisions. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
fbi_cde_state_crime_trend accepts 7 parameters: limit, state, offset, offense, end_month, start_month, response_format. Required: state, offense, end_month, start_month. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for fbi_cde_state_crime_trend: 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 Livedatalink. Nothing to install.
fbi_cde_state_crime_trend 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_cde_state_crime_trend 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_cde_state_crime_trend. 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_cde_state_crime_trend is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue