AI agents invoke clip_features to trigger actions in ArcGIS Pro Bridge MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a geoprocessing operation (Clip analysis) in ArcGIS Pro via ArcPy, which runs external spatial processing and produces output data. It is part of a server explicitly designed to 'execute ArcPy geoprocessing.' While it creates output features (Write-like), the primary action is executing a geoprocessing tool in a native environment, making Execute the appropriate category.
From the tool's definition 执行常用 Clip 分析，返回输出要素摘要和执行信息 (Executes common Clip analysis, returns output feature summary and execution info)
Documented attack patterns abuse exactly the kind of access clip_features gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ArcGIS Pro Bridge MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clip_features:
{
"version": "1",
"default": "deny",
"tools": {
"clip_features": {
"limits": [
{
"counter": "clip_features_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}clip_features stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
执行常用 Clip 分析，返回输出要素摘要和执行信息。. It is categorised as a Execute tool in the ArcGIS Pro Bridge MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ArcGIS Pro Bridge MCP Server MCP server in PolicyLayer and add a rule for clip_features: 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 ArcGIS Pro Bridge MCP Server. Nothing to install.
clip_features is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the clip_features 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 clip_features. 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.
clip_features is provided by the ArcGIS Pro Bridge MCP Server MCP server (sangwxx/arcgis-pro-bridge-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 ArcGIS Pro Bridge MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 ArcGIS Pro Bridge MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.