Dissolve geometries by attribute using geopandas.dissolve. Args: gdf_path: Path to the geospatial file. by: Column to dissolve by (optional). output_path: Optional path to save the result. Returns: Dictionary with status, message, and output info.
AI agents use dissolve_gpd 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 dissolve_gpd tool performs a reversible geospatial aggregation operation (dissolving/merging geometries by attribute values) and can optionally write results to a file. This is a data transformation and creation operation typical of Write category tools. It does not delete data irreversibly, execute arbitrary code, or access financial systems.
From the tool's definition Tool description states 'dissolve geometries by attribute' and accepts 'output_path: Optional path to save the result.' The dissolve operation aggregates geometries and the optional output_path parameter indicates file creation/modification capability.
Documented attack patterns abuse exactly the kind of access dissolve_gpd 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 dissolve_gpd:
{
"version": "1",
"default": "deny",
"tools": {
"dissolve_gpd": {
"limits": [
{
"counter": "dissolve_gpd_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} dissolve_gpd 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.
Dissolve geometries by attribute using geopandas.dissolve. Args: gdf_path: Path to the geospatial file. by: Column to dissolve by (optional). output_path: Optional path to save the result. Returns: Dictionary with status, message, and output info. 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 dissolve_gpd: 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.
dissolve_gpd 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 dissolve_gpd 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 dissolve_gpd. 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.
dissolve_gpd 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.