Employment profile for a CPF — current employer, history, monthly income, professional category. POST /v1/datasets/persons.
AI agents call employment_data to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries employment records for a CPF (Brazilian tax ID), which is sensitive personal financial and employment data. While classified as Read (no side effects, only data retrieval), the sensitivity of the data accessed and the fact it exposes detailed income and employment history warrants medium severity.
From the tool's definition Tool retrieves employment profile data including 'current employer, history, monthly income, professional category' via POST /v1/datasets/persons. Despite POST method, the description indicates data retrieval with no modification or deletion.
Documented attack patterns abuse exactly the kind of access employment_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for employment_data:
{
"version": "1",
"default": "deny",
"tools": {
"employment_data": {}
}
} employment_data 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.
Employment profile for a CPF — current employer, history, monthly income, professional category. POST /v1/datasets/persons. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for employment_data: 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 Afip. Nothing to install.
employment_data 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 employment_data 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 employment_data. 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.
employment_data is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, 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 Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.