This record as markdown: /tools/io-github-devopam-mcpg/list-active-queries.md
What list_active_queries does on Mcpg
AI agents call list_active_queries to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_active_queries is rated Low
This tool retrieves or lists active queries from the database, which is a non-destructive, informational operation. There are no side effects—it simply observes the current state of query execution. The empty description prevents higher confidence, but the name unambiguously indicates a read-only operation. Severity is low because listing active queries poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'list_active_queries' indicates retrieval of currently executing queries without modification. The verb 'list' is a read operation that queries database state.
Attacks that exploit this kind of access
The rule that runs list_active_queries safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_active_queries, this is the rule to start with:
list_active_queries is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every list_active_queries call is checked against it from then on.
Questions about list_active_queries
list_active_queries is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for list_active_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 Mcpg. Nothing to install.
list_active_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_active_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_active_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_active_queries is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue