get_search_status

検索エージェントの現在の状態と設定を確認する。「状態を確認して」「設定を見せて」「エージェントの状況は?」などの要求に対応します。

Server Langgraph Deep Search MCP Server ryotaozawa0/langgraph-deepsearch-mcp
Category Read
Risk class Low
Parameters 00 required

What get_search_status does on Langgraph Deep Search MCP Server

AI agents call get_search_status to retrieve information from Langgraph Deep Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_search_status needs a policy

This tool retrieves status and configuration information about a search agent. It performs a query operation with no capability to modify, delete, or execute external actions. The Japanese description confirms it responds to requests like 'check status', 'show settings', and 'what is the agent's situation?' — all read-only inquiries. No data modification, code execution, or destructive operations are possible.

From the tool's definition Tool name 'get_search_status' and description indicating it 'checks the current state and settings of the search agent' (検索エージェントの現在の状態と設定を確認する) — purely informational retrieval with no side effects.

Questions about get_search_status

What does the get_search_status tool do? +

検索エージェントの現在の状態と設定を確認する。「状態を確認して」「設定を見せて」「エージェントの状況は?」などの要求に対応します。. It is categorised as a Read tool in the Langgraph Deep Search MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_search_status? +

Register the Langgraph Deep Search MCP Server MCP server in PolicyLayer and add a rule for get_search_status: 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 Langgraph Deep Search MCP Server. Nothing to install.

What risk level is get_search_status? +

get_search_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_search_status? +

Yes. Add a rate_limit block to the get_search_status 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.

How do I block get_search_status completely? +

Set action: deny in the PolicyLayer policy for get_search_status. 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.

What MCP server provides get_search_status? +

get_search_status is provided by the Langgraph Deep Search MCP Server MCP server (ryotaozawa0/langgraph-deepsearch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.