Get company filing history by company number from Companies House.
AI agents call get_company_filing_history to retrieve information from GovUK MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical filing data from a public UK government register (Companies House). It has no side effects—it does not create, modify, delete, or execute operations. The data returned is already public information.
From the tool's definition Tool retrieves company filing history from Companies House by company number. The verb 'get' and the context of querying publicly available government data sources indicates data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get company filing history by company number from Companies House. It is categorised as a Read tool in the GovUK MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GovUK MCP Server MCP server in PolicyLayer and add a rule for get_company_filing_history: 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 GovUK MCP Server. Nothing to install.
get_company_filing_history 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 get_company_filing_history 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 get_company_filing_history. 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.
get_company_filing_history is provided by the GovUK MCP Server MCP server (stealth-labs-ltd/govuk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →