AI agents call progress_demo as a supporting operation in Gemini Research MCP Server workflows.
With no description available, classification relies solely on the name. 'progress_demo' suggests a demo/showcase of progress reporting, which would be read-only or purely presentational. However, confidence is low due to the absence of any description.
From the tool's definition Tool description is empty and uninformative; tool name 'progress_demo' suggests a demonstration of progress tracking functionality rather than a data-modifying operation.
Documented attack patterns abuse exactly the kind of access progress_demo gives an agent:
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 progress_demo:
{
"version": "1",
"default": "deny",
"tools": {
"progress_demo": {
"limits": [
{
"counter": "progress_demo_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} progress_demo gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
progress_demo. It is categorised as a Other tool in the Gemini Research MCP Server MCP Server, which means it performs auxiliary operations.
Register the Gemini Research MCP Server MCP server in PolicyLayer and add a rule for progress_demo: 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.
progress_demo is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the progress_demo 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 progress_demo. 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.
progress_demo 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.
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.
Free to start. No card required.
11 Gemini Research MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.