KYB — validate a CNPJ, return corporate profile, QSA, regularity, sanctions. POST /v1/checks/company.
AI agents call company_check 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 retrieves and validates corporate profile data (CNPJ lookup, QSA details, regulatory status, sanctions information) with no data modification or deletion. It is fundamentally a Read operation that queries external business registries.
From the tool's definition Tool description states: 'validate a CNPJ, return corporate profile, QSA, regularity, sanctions.' The POST endpoint performs validation and retrieval of corporate information without modifying data. KYB (Know Your Business) checks are informational queries.
Documented attack patterns abuse exactly the kind of access company_check 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 company_check:
{
"version": "1",
"default": "deny",
"tools": {
"company_check": {}
}
}company_check 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.
KYB — validate a CNPJ, return corporate profile, QSA, regularity, sanctions. POST /v1/checks/company. 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 company_check: 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.
company_check 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 company_check 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 company_check. 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.
company_check 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.