query_knowledge_graph
AI agents call query_knowledge_graph to retrieve information from Adaptive Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention 'query_' strongly suggests a read-only operation that retrieves data from the knowledge graph without modification. While the description is uninformative, the context of sibling tools and the established pattern of 'query_' prefix for read operations (similar to 'query_memory_headers') supports classification as Read.
From the tool's definition Tool name 'query_knowledge_graph' indicates querying/retrieval operation. The sibling tools on this server include write operations (add_knowledge_relation, append_daily_log) and destructive operations (delete_knowledge), positioning query_knowledge_graph as…
Attacks that exploit this kind of access
query_knowledge_graph. It is categorised as a Read tool in the Adaptive Agent MCP Server, which means it retrieves data without modifying state.
Register the Adaptive Agent MCP server in PolicyLayer and add a rule for query_knowledge_graph: 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 Adaptive Agent. Nothing to install.
query_knowledge_graph 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_graph 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_graph. 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_graph is provided by the Adaptive Agent MCP server (justforever17/adaptive-agent-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 →