gp_search_services
AI agents call gp_search_services to retrieve information from ArcGIS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations typically retrieve and list available geoprocessing services without modifying state or triggering execution. The absence of destructive, write, or execution keywords in the name suggests read-only querying. However, confidence is moderate (0.7) because the empty description prevents confirmation that this tool doesn't trigger service execution or have side effects.
From the tool's definition Tool name 'gp_search_services' indicates a search/query operation (search suggests read-only retrieval). The 'gp_' prefix suggests geoprocessing context. No description provided to confirm exact behavior.
Attacks that exploit this kind of access
gp_search_services. It is categorised as a Read tool in the ArcGIS MCP MCP Server, which means it retrieves data without modifying state.
Register the ArcGIS MCP server in PolicyLayer and add a rule for gp_search_services: 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 MCP. Nothing to install.
gp_search_services is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gp_search_services 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 gp_search_services. 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.
gp_search_services is provided by the ArcGIS MCP server (renemorenow/arcgis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →