query_knowledge
AI agents call query_knowledge to retrieve information from Vending Machine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention and context strongly suggest this is a read-only query operation against a knowledge base or vector store. No description was provided, which slightly lowers confidence, but the tool name and sibling tools (search_scripts, vector_store_add) indicate retrieval semantics with no apparent destructive or side-effect capability.
From the tool's definition Tool name 'query_knowledge' suggests a retrieval/search operation typical of knowledge base or vector store queries.
Attacks that exploit this kind of access
query_knowledge. It is categorised as a Read tool in the Vending Machine MCP Server, which means it retrieves data without modifying state.
Register the Vending Machine MCP server in PolicyLayer and add a rule for query_knowledge: 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 Vending Machine. Nothing to install.
query_knowledge 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_knowledge 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_knowledge. 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_knowledge is provided by the Vending Machine MCP server (yokiidesu/vending-machine-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 →