List all tracked queries for the user
AI agents call list_tracked_queries to retrieve information from MCP Starter for Puch AI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about previously tracked queries. It performs no write operations, does not delete data, does not execute code or commands, and does not involve financial transactions. It is a simple data retrieval/read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_tracked_queries' and description 'List all tracked queries for the user' indicate a retrieval operation that queries existing data without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List all tracked queries for the user. It is categorised as a Read tool in the MCP Starter for Puch AI MCP Server, which means it retrieves data without modifying state.
Register the MCP Starter for Puch AI MCP server in PolicyLayer and add a rule for list_tracked_queries: 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.
list_tracked_queries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_tracked_queries 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 list_tracked_queries. 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.
list_tracked_queries 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 →