business.ukcompany.details
Full details for a UK company by Companies House number — company name, type, status, SIC codes, registered address, accounts due date, confirmation statement due, charges, insolvency history (Companies House UK Gov)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/business.ukcompany.details.md
What business.ukcompany.details does on Apibase
AI agents call business.ukcompany.details 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 |
|---|---|---|---|
company_number | string | Yes | UK Companies House number (e.g. "00048839" for Barclays, "00445790" for Tesco). Get from search results |
Parameters from the server's own tool schema.
Why business.ukcompany.details is rated Low
Tool queries and returns company registration data without creating, modifying, or deleting records.
From the tool's definition Retrieves full details for a UK company; no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs business.ukcompany.details 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 business.ukcompany.details, this is the rule to start with:
business.ukcompany.details 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 business.ukcompany.details call is checked against it from then on.
Questions about business.ukcompany.details
Full details for a UK company by Companies House number — company name, type, status, SIC codes, registered address, accounts due date, confirmation statement due, charges, insolvency history (Companies House UK Gov). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
business.ukcompany.details accepts 1 parameter: company_number. Required: company_number. 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 business.ukcompany.details: 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.
business.ukcompany.details 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 business.ukcompany.details 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 business.ukcompany.details. 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.
business.ukcompany.details 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