AI agents call research_status to retrieve information from Interdeep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents information about the server's capabilities and readiness state. It is a read-only operation with no side effects, no data modification, and no external command execution. The 'show' verb confirms it queries existing state rather than performing actions. Even in a research context with sibling tools for extraction and compilation, this specific tool is purely informational.
From the tool's definition Tool name 'research_status' and description 'Show extraction capabilities and companion plugin readiness' indicate a query/display operation that retrieves and reports status information without modifying data or executing external operations.
Attacks that exploit this kind of access
Show extraction capabilities and companion plugin readiness. It is categorised as a Read tool in the Interdeep MCP Server, which means it retrieves data without modifying state.
Register the Interdeep MCP server in PolicyLayer and add a rule for research_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 Interdeep. Nothing to install.
research_status 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 research_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.
Set action: deny in the PolicyLayer policy for research_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.
research_status is provided by the Interdeep MCP server (mistakeknot/interdeep). 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 →