research_status
AI agents call research_status to retrieve information from NotebookLM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve the status of research operations within NotebookLM rather than modify, execute, or destroy data. Status checks are non-destructive read operations. Low severity because knowing research status poses minimal risk; confidence is moderate-to-good (0.75) because the description is absent but the name and server context strongly suggest a read operation.
From the tool's definition Tool name 'research_status' indicates a status-checking operation; server capabilities show read-only inquiry functions (list, get, status patterns).
Attacks that exploit this kind of access
research_status. It is categorised as a Read tool in the NotebookLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NotebookLM MCP Server 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 NotebookLM MCP Server. 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 NotebookLM MCP Server MCP server (ran-ai-agency/notebooklm-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 →