gp_service_info
AI agents call gp_service_info 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.
The tool description is empty, which reduces confidence slightly. However, the naming convention strongly suggests this retrieves metadata or status information about a geoprocessing service without modifying state. Geoprocessing service info queries are standard read operations in ArcGIS. The tool carries minimal risk if misused by an AI agent, as it only exposes service information.
From the tool's definition Tool name 'gp_service_info' indicates it retrieves information about a geoprocessing service. The suffix '_info' and naming pattern matching sibling tools like 'admin_servers_list', 'admin_services_health', and 'admin_system_info' (all informational/read…
Attacks that exploit this kind of access
gp_service_info. 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_service_info: 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_service_info 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_service_info 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_service_info. 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_service_info 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 →