Create a categorized style for features (polygon, line, point) using column values. Args: style_name (str): New style name. column_name (str): Column to base categories on. column_distinct_values: Values (categories) to style. workspace (str, optional): Workspace for the style. color_ramp (str, o...
AI agents use create_catagorized_featurestyle to create or update resources in GeoServer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GeoServer MCP Server environment.
This tool creates a new geospatial styling resource in GeoServer, which is a Write operation (reversible data creation/modification). The blast radius is medium because misconfiguration could render geospatial visualizations incorrect or unusable across multiple layers, but the operation itself does not delete, destroy, or execute arbitrary code. The style can be modified or deleted afterward.
From the tool's definition Tool creates a new style resource ('Create a categorized style') via GeoServer REST API. The parameters include 'style_name' (new style name) and optional 'workspace', indicating a reversible creation operation.
Documented attack patterns abuse exactly the kind of access create_catagorized_featurestyle gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GeoServer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_catagorized_featurestyle:
{
"version": "1",
"default": "deny",
"tools": {
"create_catagorized_featurestyle": {
"limits": [
{
"counter": "create_catagorized_featurestyle_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_catagorized_featurestyle 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 a categorized style for features (polygon, line, point) using column values. Args: style_name (str): New style name. column_name (str): Column to base categories on. column_distinct_values: Values (categories) to style. workspace (str, optional): Workspace for the style. color_ramp (str, optional): Color ramp. geom_type (str, optional): Geometry type. Returns: dict: API response. It is categorised as a Write tool in the GeoServer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GeoServer MCP Server MCP server in PolicyLayer and add a rule for create_catagorized_featurestyle: 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 GeoServer MCP Server. Nothing to install.
create_catagorized_featurestyle 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_catagorized_featurestyle 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_catagorized_featurestyle. 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_catagorized_featurestyle is provided by the GeoServer MCP Server MCP server (mahdin75/geoserver-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GeoServer 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.
56 GeoServer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.