generate_thematic_map
AI agents use generate_thematic_map to create or update resources in SB OGC MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SB OGC MCP environment.
An AI agent can call generate_thematic_map faster than any human can review — one bad instruction and it creates or modifies resources in SB OGC MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
generate_thematic_map. It is categorised as a Write tool in the SB OGC MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SB OGC MCP server in PolicyLayer and add a rule for generate_thematic_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 SB OGC MCP. Nothing to install.
generate_thematic_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 generate_thematic_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 generate_thematic_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.
generate_thematic_map is provided by the SB OGC MCP server (studio-bereikbaar/sb-ogc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →