Medium Risk

track_login

Notify Legiti of a login attempt (successful or failed). Convenience wrapper over track_auth that hard-codes action=

How to control track_login ↓

What track_login does on Mcp Afip

AI agents use track_login 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 track_login needs a policy

This tool sends/posts a notification about a login event to a third-party fraud detection service (Legiti). It creates a record of the event, which is a reversible write operation. It does not execute code, delete data, or involve financial transactions. Severity is low since it merely logs/reports an authentication event, though misuse could involve sending false login signals.

From the tool's definition Notify Legiti of a login attempt (successful or failed). Convenience wrapper over track_auth that hard-codes action=

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

How to control track_login

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

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

track_login 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 track_login

What does the track_login tool do? +

Notify Legiti of a login attempt (successful or failed). Convenience wrapper over track_auth that hard-codes action=. 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 track_login? +

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

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

Can I rate-limit track_login? +

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

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

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