Get super secure person with significant control
AI agents call get_psc_super_secure 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 PSC (Person with Significant Control) data from Companies House, which is a read-only query operation. However, PSC information is sensitive personal/business data (identifies individuals with ownership stakes), elevating severity from low to medium due to privacy implications and potential misuse for targeting, fraud, or social engineering.
From the tool's definition Tool name 'get_psc_super_secure' and description 'Get super secure person with significant control' indicate retrieval of person with significant control (PSC) data, which is a read operation.
Documented attack patterns abuse exactly the kind of access get_psc_super_secure 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_super_secure:
{
"version": "1",
"default": "deny",
"tools": {
"get_psc_super_secure": {}
}
} get_psc_super_secure 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 super secure person with significant control. 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_super_secure: 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_super_secure 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_super_secure 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_super_secure. 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_super_secure 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.