research_followup

THE RISK

Low Risk

Why research_followup needs a policy

The description is completely empty, so the classification must rely solely on the tool name. Based on the name 'research_followup' and the server context (AI-powered research, web search, session management), it likely performs a follow-up research query (a Read operation). However, without a description, confidence is very low.

From the tool's definition Tool name is 'research_followup' and description is empty or uninformative.

Documented attack patterns abuse exactly the kind of access research_followup gives an agent:

POLICY

How to control research_followup

PolicyLayer is an MCP gateway — it sits between your AI agents and Gemini Research MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for research_followup:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "research_followup": {
      "limits": [
        {
          "counter": "research_followup_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

research_followup gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register Gemini Research MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Gemini Research MCP Server tools

Execute research_deep research_deep Execute research_deep_max research_deep_max Write export_research_session export_research_session Read fetch_webpage fetch_webpage Read inspect_mcp_server_for_gemini Inspect a remote MCP server before passing it to Gemini Deep Research. Read list_format_templates list_format_templates Read list_research_sessions list_research_sessions Other progress_demo progress_demo

All 11 Gemini Research MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about research_followup

What does the research_followup tool do? +

research_followup. It is categorised as a Other tool in the Gemini Research MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on research_followup? +

Register the Gemini Research MCP Server MCP server in PolicyLayer and add a rule for research_followup: 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 Gemini Research MCP Server. Nothing to install.

What risk level is research_followup? +

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

Can I rate-limit research_followup? +

Yes. Add a rate_limit block to the research_followup 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 research_followup completely? +

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

research_followup is provided by the Gemini Research MCP Server MCP server (machinemates-ai/gemini-research-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gemini Research MCP Server tool call.

Start from Gemini Research MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →