arcgis_auth_save_profile
AI agents use arcgis_auth_save_profile to create or update resources in ArcGIS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ArcGIS MCP environment.
This tool creates or modifies authentication profile data, which is reversible (profiles can be updated or removed). While the empty description limits confidence, the naming pattern and server context clearly indicate it performs a write operation on authentication configuration.
From the tool's definition Tool name 'arcgis_auth_save_profile' indicates it saves authentication profile data. The server context shows this is part of ArcGIS authentication management (sibling tools include 'arcgis_auth_connect' and 'arcgis_auth_status').
Attacks that exploit this kind of access
arcgis_auth_save_profile. It is categorised as a Write tool in the ArcGIS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ArcGIS MCP server in PolicyLayer and add a rule for arcgis_auth_save_profile: 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.
arcgis_auth_save_profile 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 arcgis_auth_save_profile 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 arcgis_auth_save_profile. 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.
arcgis_auth_save_profile 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 →