[OCD] コンテキストツリー(目次)を取得 パラメータ - rootIds: Context Root の id 配列（list_context_roots で取得した id をそのまま使用） - patterns (optional): include glob（rootId 相対）。指定時は depth より優先 - exclude (optional): exclude glob（rootId 相対）。tree から除外 重要: list_context_roots で返却された id を使用してください。 path フィールド（実際のファイルシステムパス）は使用しないでください...
AI agents call ocd_get_context_tree 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.
This tool queries and returns structured data (a hierarchical tree view) without modifying, creating, or deleting any data. It is a pure read operation with optional filtering. The emphasis on using correct IDs and avoiding filesystem paths reflects safe query semantics, not side effects.
From the tool's definition Tool name 'ocd_get_context_tree' and description indicate it 'retrieves' (取得) a context tree/table of contents with optional filtering via glob patterns. Parameters are read-only: rootIds, patterns (include glob), and exclude (exclude glob).
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
[OCD] コンテキストツリー(目次)を取得 パラメータ - rootIds: Context Root の id 配列（list_context_roots で取得した id をそのまま使用） - patterns (optional): include glob（rootId 相対）。指定時は depth より優先 - exclude (optional): exclude glob（rootId 相対）。tree から除外 重要: list_context_roots で返却された id を使用してください。 path フィールド（実際のファイルシステムパス）は使用しないでください。 例: - 単一: rootIds: [. 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 ocd_get_context_tree: 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.
ocd_get_context_tree 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 ocd_get_context_tree 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 ocd_get_context_tree. 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.
ocd_get_context_tree 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 →