share_group_audit
AI agents call share_group_audit 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.
Despite the empty description lowering confidence, 'audit' strongly suggests a reporting/querying function rather than modification, deletion, or execution. The context of sibling tools (admin_*, auth_*, docs_get) suggests this is part of ArcGIS administrative query suite.
From the tool's definition Tool name 'share_group_audit' suggests auditing or reviewing group sharing/permissions status. The 'audit' component typically implies querying logs or status without modification. No description provided to confirm read-only intent.
Attacks that exploit this kind of access
share_group_audit. 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 share_group_audit: 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.
share_group_audit 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 share_group_audit 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 share_group_audit. 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.
share_group_audit 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 →