query_knowledge
Retrieve structured knowledge from Agent Module verticals. Returns deterministic, validated knowledge nodes. Index layer always free. All 4 content layers available via trial key on ethics.
This record as markdown: /tools/dev-agent-module-mcp/query-knowledge.md
What query_knowledge does on Agent Module
AI agents call query_knowledge to retrieve information from Agent Module without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
node | string | — | Specific node ID to retrieve. Omit for root index. |
token | string | — | Membership or trial key (am_live_, am_test_, or am_trial_ prefix). Required for content layers on gated verticals. |
vertical | string | Yes | Knowledge vertical to query. |
Parameters from the server's own tool schema.
Why query_knowledge is rated Low
The tool retrieves data from knowledge bases without modifying, deleting, or executing code. While it accesses structured knowledge, the operation is fundamentally a query that returns information. The mention of 'trial key' and access control does not change the underlying function—it remains a read operation.
From the tool's definition Tool name 'query_knowledge' and description 'Retrieve structured knowledge' indicate a read-only retrieval operation. No mutation, deletion, or execution capabilities are mentioned.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs query_knowledge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Module, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_knowledge, this is the rule to start with:
query_knowledge 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 Agent Module, apply this rule, and every query_knowledge call is checked against it from then on.
Questions about query_knowledge
Retrieve structured knowledge from Agent Module verticals. Returns deterministic, validated knowledge nodes. Index layer always free. All 4 content layers available via trial key on ethics. It is categorised as a Read tool in the Agent Module MCP Server, which means it retrieves data without modifying state.
query_knowledge accepts 3 parameters: node, token, vertical. Required: vertical. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Module 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 Agent Module. 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 Agent Module MCP server (https://api.agent-module.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Module, and thousands of servers like it.
This server
Across the catalogue