Create a new featurestore in the given workspace. Args: workspace (str): Target workspace. name (str): Featurestore name. params (dict): Connection/configuration parameters. Returns: dict: Details of the created featurestore.
AI agents use create_featurestore 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 data store configuration, which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or read-only query (not Read). The medium severity reflects that misconfiguration could affect geospatial data access and integrity, but the operation itself is reversible through deletion or modification.
From the tool's definition Tool description states 'Create a new featurestore in the given workspace' with return of 'Details of the created featurestore', indicating data creation via REST API.
Documented attack patterns abuse exactly the kind of access create_featurestore 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_featurestore:
{
"version": "1",
"default": "deny",
"tools": {
"create_featurestore": {
"limits": [
{
"counter": "create_featurestore_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_featurestore 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 new featurestore in the given workspace. Args: workspace (str): Target workspace. name (str): Featurestore name. params (dict): Connection/configuration parameters. Returns: dict: Details of the created featurestore. 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_featurestore: 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_featurestore 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_featurestore 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_featurestore. 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_featurestore 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.