AI agents call get_company_structure to retrieve information from Zefix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves company structural information from a public register without side effects. It is a query/fetch operation that returns data without creating, modifying, deleting, or executing actions. Confidence is 0.85 rather than higher due to empty tool description, though context from sibling tools and server purpose strongly suggests read-only retrieval.
From the tool's definition Tool name 'get_company_structure' and server description indicate retrieval of 'detailed information about Swiss companies' and 'corporate structures' from the Zefix register. No modification, deletion, or execution described.
Attacks that exploit this kind of access
get_company_structure. It is categorised as a Read tool in the Zefix MCP Server, which means it retrieves data without modifying state.
Register the Zefix MCP server in PolicyLayer and add a rule for get_company_structure: 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 Zefix. Nothing to install.
get_company_structure 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_structure 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_structure. 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_structure is provided by the Zefix MCP server (johnphilipp/mcp-server-zefix). 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 →