AI agents use create_web_map to create or update resources in GIS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GIS MCP Server environment.
The name implies creation of a new resource (Write category), which is typically reversible. Without a description, it's unclear if there are destructive or execute-level side effects. Confidence is low due to the empty description. Severity is medium since creating a web map could involve publishing data or triggering external operations, but is likely a standard write operation.
From the tool's definition Tool name 'create_web_map' suggests creating a new artifact (a web map), but the description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access create_web_map gives an agent:
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 create_web_map:
{
"version": "1",
"default": "deny",
"tools": {
"create_web_map": {
"limits": [
{
"counter": "create_web_map_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_web_map stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_web_map. It is categorised as a Write tool in the GIS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GIS MCP Server MCP server in PolicyLayer and add a rule for create_web_map: 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.
create_web_map is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_web_map 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 create_web_map. 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.
create_web_map 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.
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.