gov.ukpolice.outcomes
Case outcomes (charged, acquitted, action taken, etc.) for crimes at a UK coordinate in a given month. Useful for property safety scoring. OGL v3.0
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.ukpolice.outcomes.md
What gov.ukpolice.outcomes does on Apibase
AI agents call gov.ukpolice.outcomes 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 of the location to query (e.g. 51.5074). |
lng | number | Yes | Longitude of the location to query (e.g. -0.1278). |
date | string | — | Month in YYYY-MM format. Defaults to latest available month. |
limit | integer | — | Max outcome records to return (default 100, max 500). |
Parameters from the server's own tool schema.
Why gov.ukpolice.outcomes is rated Low
Retrieves public crime outcome data; no side effects or data modification.
From the tool's definition Case outcomes for crimes at UK coordinate in given month. OGL v3.0
Attacks that exploit this kind of access
The rule that runs gov.ukpolice.outcomes 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.outcomes, this is the rule to start with:
gov.ukpolice.outcomes 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.outcomes call is checked against it from then on.
Questions about gov.ukpolice.outcomes
Case outcomes (charged, acquitted, action taken, etc.) for crimes at a UK coordinate in a given month. Useful for property safety scoring. OGL v3.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gov.ukpolice.outcomes accepts 4 parameters: lat, lng, date, limit. 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.outcomes: 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.outcomes 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.outcomes 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.outcomes. 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.outcomes 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