Low Risk

get_download_stats

Get download statistics and limits

How to control get_download_stats ↓

What get_download_stats does on Geo

AI agents call get_download_stats to retrieve information from Geo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_download_stats needs a policy

This is a read-only query tool that returns metadata about download activity and constraints. It has no side effects, does not modify or delete data, does not execute code or commands, and does not involve financial transactions. It fits squarely in the Read category with low severity because misuse would only expose usage statistics, posing minimal risk.

From the tool's definition Tool name and description indicate it 'Get download statistics and limits' — retrieves status information about downloads without modifying, deleting, or executing external operations.

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

How to control get_download_stats

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_download_stats": {}
  }
}

get_download_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Geo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_download_stats

What does the get_download_stats tool do? +

Get download statistics and limits. It is categorised as a Read tool in the Geo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_download_stats? +

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

What risk level is get_download_stats? +

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

Can I rate-limit get_download_stats? +

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

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

get_download_stats is provided by the Geo MCP server (mcpmed/geomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Geo tool call.

Start from Geo, 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 Geo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.