Get queries analytics for an agent.
AI agents call get_queries_report to retrieve information from CustomGPT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analytics/reporting data about queries for an agent. The verb 'Get' and the context of 'queries analytics' clearly indicate a read-only operation with no side effects, data modification, execution of external operations, or financial implications. The low severity reflects minimal blast radius if misused—an agent could at most gather information about query patterns.
From the tool's definition Tool name 'get_queries_report' and description 'Get queries analytics for an agent' indicate a retrieval operation that queries and returns analytics data without modifying state.
Attacks that exploit this kind of access
Get queries analytics for an agent. It is categorised as a Read tool in the CustomGPT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CustomGPT MCP Server MCP server in PolicyLayer and add a rule for get_queries_report: 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 CustomGPT MCP Server. Nothing to install.
get_queries_report 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 get_queries_report 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 get_queries_report. 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.
get_queries_report is provided by the CustomGPT MCP Server MCP server (poll-the-people/customgpt-mcp). 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 →