関連プロジェクトの一覧を取得します。設定ファイルで定義されたものとadd_related_projectで追加されたものの両方を表示します。
AI agents call list_related_projects to retrieve information from Search Docs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation with no side effects. It queries and returns information about related projects without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could retrieve unwanted project metadata but cannot cause damage or alter state. This clearly fits the Read category.
From the tool's definition Tool name 'list_related_projects' and description state it 'retrieves' or 'gets a list' (取得します) of related projects. No modification, deletion, or execution is mentioned. It simply displays/lists existing data from configuration and previously added items.
Attacks that exploit this kind of access
関連プロジェクトの一覧を取得します。設定ファイルで定義されたものとadd_related_projectで追加されたものの両方を表示します。. It is categorised as a Read tool in the Search Docs MCP Server, which means it retrieves data without modifying state.
Register the Search Docs MCP server in PolicyLayer and add a rule for list_related_projects: 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 Search Docs. Nothing to install.
list_related_projects 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_related_projects 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_related_projects. 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_related_projects is provided by the Search Docs MCP server (otolab/search-docs). 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 →