Notify Legiti of a login attempt (successful or failed). Convenience wrapper over track_auth that hard-codes action=
AI agents use track_login to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool creates or modifies audit log records by tracking and notifying of login attempts. It is a Write operation because it persistently records authentication events with side effects that are reversible (logs can be deleted or modified). While it has audit/security implications, the core function is data recording rather than code execution or financial movement.
From the tool's definition Tool name 'track_login' indicates logging/recording of authentication events. Description states it 'Notify Legiti of a login attempt' and 'hard-codes action=' in an auth-tracking context, suggesting it writes audit/log records.
Documented attack patterns abuse exactly the kind of access track_login 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 track_login:
{
"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.
Free to start. No card required.
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 Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 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 Ap2. Nothing to install.
track_login is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
track_login 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.