Manually track a request for analytics purposes
AI agents use track-request to create or update resources in NestJS MCP Server Module — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NestJS MCP Server Module environment.
This tool writes analytics tracking data. It creates a record of a request for analytics purposes, which is a reversible write operation with low blast radius since it only affects analytics/logging data, not core application data.
From the tool's definition 'Manually track a request for analytics purposes' — creates/records analytics data
Attacks that exploit this kind of access
Manually track a request for analytics purposes. It is categorised as a Write tool in the NestJS MCP Server Module MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NestJS MCP Server Module MCP server in PolicyLayer and add a rule for track-request: 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 NestJS MCP Server Module. Nothing to install.
track-request 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-request 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-request. 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-request is provided by the NestJS MCP Server Module MCP server (rekog-labs/mcp-nest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →