Knowledge Baseで利用可能なContext Root一覧を取得します
AI agents call list_context_roots to retrieve information from OCD - Organized Context Datastore (MCP) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists available Context Root entries from a knowledge base. This is a read-only query operation that does not create, modify, delete, or execute anything. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'list_context_roots' and description 'Knowledge Base で利用可能なContext Root一覧を取得します' (retrieves a list of available Context Roots in the Knowledge Base) indicate a retrieval operation with no modification or execution of external processes.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Knowledge Baseで利用可能なContext Root一覧を取得します. It is categorised as a Read tool in the OCD - Organized Context Datastore (MCP) MCP Server, which means it retrieves data without modifying state.
Register the OCD - Organized Context Datastore (MCP) MCP server in PolicyLayer and add a rule for list_context_roots: 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 OCD - Organized Context Datastore (MCP). Nothing to install.
list_context_roots 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_context_roots 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_context_roots. 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_context_roots is provided by the OCD - Organized Context Datastore (MCP) MCP server (teamstove/organized-context-datastore-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 →