share_audit_by_owner
AI agents call share_audit_by_owner 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 appears designed to retrieve audit or sharing data rather than modify it. The 'audit' component typically indicates inspection/logging functionality (Read), while 'by_owner' suggests filtering. However, confidence is reduced due to the empty description, which prevents confirmation of scope and potential side effects.
From the tool's definition Tool name 'share_audit_by_owner' suggests querying or listing sharing/audit information filtered by owner. No description provided, but naming pattern aligns with audit retrieval operations common in the 'admin' and 'arcgis_auth' tool families on this server.
Attacks that exploit this kind of access
share_audit_by_owner. 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_audit_by_owner: 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_audit_by_owner 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_audit_by_owner 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_audit_by_owner. 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_audit_by_owner 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 →