server_service_restart
AI agents invoke server_service_restart to trigger actions in ArcGIS MCP. 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.
Restarting a server service is an Execute-class action: it runs an operation whose effects depend on which service is targeted. The blast radius is high because restarting critical services can cause extended downtime, disrupt users, and potentially cause data loss if in-flight transactions are interrupted. While not permanently destructive or financial, it causes significant operational disruption.
From the tool's definition Tool name 'server_service_restart' indicates restarting a server service, which triggers an external operation with side effects (service downtime, interruption of operations).
Attacks that exploit this kind of access
server_service_restart. It is categorised as a Execute tool in the ArcGIS MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ArcGIS MCP server in PolicyLayer and add a rule for server_service_restart: 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.
server_service_restart 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 server_service_restart 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 server_service_restart. 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.
server_service_restart 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 →