Add or update a tracked query for LLM visibility monitoring
AI agents use add_tracking_query to create or update resources in MCP Starter for Puch AI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Starter for Puch AI environment.
This tool creates or modifies stored queries for monitoring purposes. It's a Write operation because it irreversibly adds/updates data (tracked queries) that will persist and affect future monitoring behavior.
From the tool's definition Tool name 'add_tracking_query' and description 'Add or update a tracked query' indicate data modification—creating or updating records in a tracking system.
Attacks that exploit this kind of access
Add or update a tracked query for LLM visibility monitoring. It is categorised as a Write tool in the MCP Starter for Puch AI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Starter for Puch AI MCP server in PolicyLayer and add a rule for add_tracking_query: 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 Starter for Puch AI. Nothing to install.
add_tracking_query 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 add_tracking_query 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 add_tracking_query. 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.
add_tracking_query is provided by the MCP Starter for Puch AI MCP server (kulraj69/mcp-llm). 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 →