tracking.identify · MCP Fullstack MCP: Risk & Policy

WHAT IT DOES

What tracking.identify does on MCP Fullstack

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

WHY IT NEEDS A POLICY

Why tracking.identify needs a policy

'Identify user traits' implies associating traits/properties with a user identity in an analytics or tracking system, which is a write operation (creating or updating user profile data). This is analogous to analytics identity calls (e.g., Segment's identify()) that persist user attributes. It is reversible/updatable, placing it in Write rather than Destructive.

From the tool's definition Identify user traits

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tracking.identify Rate-limited

tracking.identify 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tracking.identify": {
      "limits": [
        {
          "counter": "tracking.identify_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Fullstack, so you can run agents against it safely.

FAQ

Questions about tracking.identify

What does the tracking.identify tool do? +

Identify user traits. It is categorised as a Write tool in the MCP Fullstack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tracking.identify? +

Register the MCP Fullstack MCP server in PolicyLayer and add a rule for tracking.identify: 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 Fullstack. Nothing to install.

What risk level is tracking.identify? +

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

Can I rate-limit tracking.identify? +

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

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

tracking.identify is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.