Low Risk

download_species_occurrences

download_species_occurrences

How to control download_species_occurrences ↓

What download_species_occurrences does on GIS MCP Server

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

Low Risk

Why download_species_occurrences needs a policy

The tool name indicates a data retrieval operation fetching species occurrence records, typical of read-only GIS queries against biological datasets. While the description is empty (reducing confidence), the naming pattern and context within a GIS server that performs geometric operations and spatial analysis suggests this fetches pre-existing data rather than modifying, executing external code, deleting, or moving…

From the tool's definition Tool name 'download_species_occurrences' indicates retrieval of species occurrence data. No description provided, but the verb 'download' combined with the GIS server context suggests querying/fetching geospatial biodiversity data without modification or…

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

How to control download_species_occurrences

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

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

download_species_occurrences 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 GIS MCP Server — 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 download_species_occurrences

What does the download_species_occurrences tool do? +

download_species_occurrences. It is categorised as a Read tool in the GIS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on download_species_occurrences? +

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

What risk level is download_species_occurrences? +

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

Can I rate-limit download_species_occurrences? +

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

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

download_species_occurrences is provided by the GIS MCP Server MCP server (mahdin75/gis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GIS MCP Server tool call.

Start from GIS 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.

98 GIS MCP Server 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.