CNPJ lookup — razão social, fantasia, founding date, paid-in capital, partners, address, CNAE. POST /v1/datasets/companies.
AI agents call companies_lookup to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a dataset to retrieve public company registration information. It has no side effects—it does not create, modify, delete, or execute external operations. It is a data retrieval operation that returns read-only company metadata. The use of POST for the lookup operation does not change the fundamental nature of the action as a query/fetch operation.
From the tool's definition Tool performs 'CNPJ lookup' retrieving company data fields (razão social, fantasia, founding date, paid-in capital, partners, address, CNAE) via POST /v1/datasets/companies endpoint. The POST method is used for querying/retrieval rather than modification.
Documented attack patterns abuse exactly the kind of access companies_lookup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for companies_lookup:
{
"version": "1",
"default": "deny",
"tools": {
"companies_lookup": {}
}
}companies_lookup 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.
CNPJ lookup — razão social, fantasia, founding date, paid-in capital, partners, address, CNAE. POST /v1/datasets/companies. It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for companies_lookup: 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 Mcp Ap2. Nothing to install.
companies_lookup 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 companies_lookup 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 companies_lookup. 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.
companies_lookup is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, 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.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.