Low Risk

onboarding_process_get

Get status + results of an onboarding process. Each step (KYC, biometrics, signature) reports its own verdict. GET /v1/onboarding/processes/{process_id}.

How to control onboarding_process_get ↓

What onboarding_process_get does on Mcp Afip

AI agents call onboarding_process_get 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.

Low Risk

Why onboarding_process_get needs a policy

This tool retrieves information about an onboarding process (KYC, biometrics, signature verification steps) but performs no data modification, deletion, execution, or financial operations. It is a straightforward status query with no side effects, fitting the Read category.

From the tool's definition Tool description explicitly states 'Get status + results' and uses HTTP GET method. The endpoint pattern GET /v1/onboarding/processes/{process_id} is a read-only retrieval operation that queries the status of an onboarding process without modifying data.

Documented attack patterns abuse exactly the kind of access onboarding_process_get gives an agent:

How to control onboarding_process_get

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 onboarding_process_get:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "onboarding_process_get": {}
  }
}

onboarding_process_get is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about onboarding_process_get

What does the onboarding_process_get tool do? +

Get status + results of an onboarding process. Each step (KYC, biometrics, signature) reports its own verdict. GET /v1/onboarding/processes/{process_id}. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on onboarding_process_get? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for onboarding_process_get: 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.

What risk level is onboarding_process_get? +

onboarding_process_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit onboarding_process_get? +

Yes. Add a rate_limit block to the onboarding_process_get 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.

How do I block onboarding_process_get completely? +

Set action: deny in the PolicyLayer policy for onboarding_process_get. 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.

What MCP server provides onboarding_process_get? +

onboarding_process_get 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.

Enforce policy on every Mcp Afip tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.