Tracks prompt optimization analytics and performance metrics
AI agents use track_analytics to create or update resources in PromptForge MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PromptForge MCP Server environment.
The tool writes analytics and performance metric data to a store. It does not read-only (it actively records/tracks), does not execute code, and poses minimal blast radius if misused — at worst it could corrupt analytics records, but data is reversible and low-impact.
From the tool's definition 'Tracks prompt optimization analytics and performance metrics' — recording/storing analytics data constitutes a write operation (creating or updating records)
Attacks that exploit this kind of access
Tracks prompt optimization analytics and performance metrics. It is categorised as a Write tool in the PromptForge MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PromptForge MCP Server MCP server in PolicyLayer and add a rule for track_analytics: 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 PromptForge MCP Server. Nothing to install.
track_analytics 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_analytics 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_analytics. 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_analytics is provided by the PromptForge MCP Server MCP server (stevekaplanai/promptforge-mcp-server). 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 →