gov.ukpolice.crimes_near
Street-level UK crime records within 1 mile of a coordinate for a given month (England + Wales, 43 forces). Filter by crime category. Returns up to 500 records with category, location, outcome status. OGL v3.0 (commercial OK)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.ukpolice.crimes-near.md
What gov.ukpolice.crimes_near does on Apibase
AI agents call gov.ukpolice.crimes_near 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 |
|---|---|---|---|
lat | number | Yes | Latitude (e.g. 51.5074 for central London). UK area only. |
lng | number | Yes | Longitude (e.g. -0.1278 for central London). |
date | string | — | Month in YYYY-MM format (e.g. "2024-06"). Defaults to latest available month if omitted. |
limit | integer | — | Max crime records to return (default 100, max 500). |
category | string | — | Crime category slug — "all-crime" (default), "burglary", "violent-crime", "drugs", "robbery", "shoplifting", "vehicle-crime", "anti-social-behaviour", etc. |
Parameters from the server's own tool schema.
Why gov.ukpolice.crimes_near is rated Low
Tool queries public crime data with no side effects, suitable for informational use only.
From the tool's definition retrieves street-level UK crime records, no modifications or deletions
Attacks that exploit this kind of access
The rule that runs gov.ukpolice.crimes_near 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 gov.ukpolice.crimes_near, this is the rule to start with:
gov.ukpolice.crimes_near 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 gov.ukpolice.crimes_near call is checked against it from then on.
Questions about gov.ukpolice.crimes_near
Street-level UK crime records within 1 mile of a coordinate for a given month (England + Wales, 43 forces). Filter by crime category. Returns up to 500 records with category, location, outcome status. OGL v3.0 (commercial OK). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gov.ukpolice.crimes_near accepts 5 parameters: lat, lng, date, limit, category. Required: lat, lng. 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 gov.ukpolice.crimes_near: 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.
gov.ukpolice.crimes_near 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 gov.ukpolice.crimes_near 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 gov.ukpolice.crimes_near. 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.
gov.ukpolice.crimes_near 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