query_context
AI agents call query_context to retrieve information from PromStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context suggest it queries or retrieves context information, most likely related to prompt metadata or environment context. Sibling tools are all read-only operations (list, get, select). The empty description reduces confidence, but the pattern indicates a retrieval operation with no side effects. Classified as Read with low severity due to lack of direct user impact from context queries alone.
From the tool's definition Tool name 'query_context' combined with sibling tools (get_prompt, list_prompts, select_prompt) that are clearly retrieval-focused. The server description emphasizes 'prompt discovery' and 'selection' rather than modification.
Attacks that exploit this kind of access
query_context. It is categorised as a Read tool in the PromStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PromStack MCP Server MCP server in PolicyLayer and add a rule for query_context: 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 PromStack MCP Server. Nothing to install.
query_context 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 query_context 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 query_context. 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.
query_context is provided by the PromStack MCP Server MCP server (promstack-1/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 →