Publish a featurestore using a SQL view definition. Args: workspace (str): Workspace context. store_name (str): Featurestore. params (dict): Featurestore details. sqlview_params (list): SQL view parameter dicts. Returns: dict: Publication outcome.
AI agents use publish_featurestore_sqlview 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 or publishes a new featurestore and SQL view definition in GeoServer. While similar 'create' operations exist on this server (create_featurestore, create_layer), the SQL view aspect introduces potential for complex data exposure through database query definitions. The tool modifies GeoServer's data configuration, making it a Write operation.
From the tool's definition Tool performs 'Publish a featurestore using a SQL view definition' which creates or modifies data resources in GeoServer.
Documented attack patterns abuse exactly the kind of access publish_featurestore_sqlview 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 publish_featurestore_sqlview:
{
"version": "1",
"default": "deny",
"tools": {
"publish_featurestore_sqlview": {
"limits": [
{
"counter": "publish_featurestore_sqlview_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}publish_featurestore_sqlview 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.
Publish a featurestore using a SQL view definition. Args: workspace (str): Workspace context. store_name (str): Featurestore. params (dict): Featurestore details. sqlview_params (list): SQL view parameter dicts. Returns: dict: Publication outcome. 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 publish_featurestore_sqlview: 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.
publish_featurestore_sqlview 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 publish_featurestore_sqlview 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 publish_featurestore_sqlview. 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.
publish_featurestore_sqlview 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.