Medium Risk

link_session_to_user

Send a $link_session_to_user event to Sift

How to control link_session_to_user ↓

What link_session_to_user does on Mcp Afip

AI agents use link_session_to_user to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.

Medium Risk

Why link_session_to_user needs a policy

This tool sends an event to Sift linking a session to a user account. While not directly mutating AFIP tax data, it creates a new association/record in an external system that can be reversed or updated. It falls under Write rather than Execute because it appears to be a specific event submission (reversible state change) rather than arbitrary code execution.

From the tool's definition 'Send a $link_session_to_user event to Sift' — creates or modifies session-to-user linkage in an external service (Sift, a fraud detection platform)

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

How to control link_session_to_user

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "link_session_to_user": {
      "limits": [
        {
          "counter": "link_session_to_user_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

link_session_to_user stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about link_session_to_user

What does the link_session_to_user tool do? +

Send a $link_session_to_user event to Sift. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on link_session_to_user? +

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

link_session_to_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit link_session_to_user? +

Yes. Add a rate_limit block to the link_session_to_user 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 link_session_to_user completely? +

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

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