Get individual PSC full record
AI agents call get_psc_individual_full_record to retrieve information from Companies House MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data with no modification capability—purely a Read operation. However, severity is elevated to 'high' rather than 'low' because PSC records contain sensitive personal information (names, addresses, dates of birth, nationality) and details about company ownership/control that could enable identity fraud, corporate espionage, or targeting of individuals for harassment or exploitation.
From the tool's definition Tool name 'get_psc_individual_full_record' and description 'Get individual PSC full record' indicate retrieval of Persons of Significant Control (PSC) records.
Documented attack patterns abuse exactly the kind of access get_psc_individual_full_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Companies House MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_psc_individual_full_record:
{
"version": "1",
"default": "deny",
"tools": {
"get_psc_individual_full_record": {}
}
} get_psc_individual_full_record is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get individual PSC full record. It is categorised as a Read tool in the Companies House MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Companies House MCP Server MCP server in PolicyLayer and add a rule for get_psc_individual_full_record: 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 Companies House MCP Server. Nothing to install.
get_psc_individual_full_record 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_psc_individual_full_record 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_psc_individual_full_record. 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_psc_individual_full_record is provided by the Companies House MCP Server MCP server (stefanoamorelli/companies-house-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Companies House MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Companies House MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.