AI agents call list_broken_data_sources to retrieve information from Arcmap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about broken or missing data source references in ArcMap layers and tables. It performs a diagnostic read operation to identify data sources that ArcMap cannot locate, but does not modify, delete, or execute any operations on those sources. The blast radius is minimal—an AI agent cannot cause damage by querying this information.
From the tool's definition Tool name 'list_broken_data_sources' and description 'Lista las capas/tablas con la fuente de datos ROTA' (Lists layers/tables with broken data sources) indicates querying/inspecting the state of data sources in ArcMap without modifying or deleting them.
Attacks that exploit this kind of access
Lista las capas/tablas con la fuente de datos ROTA (rutas que ArcMap no encuentra,. It is categorised as a Read tool in the Arcmap MCP Server, which means it retrieves data without modifying state.
Register the Arcmap MCP server in PolicyLayer and add a rule for list_broken_data_sources: 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 Arcmap. Nothing to install.
list_broken_data_sources 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 list_broken_data_sources 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 list_broken_data_sources. 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.
list_broken_data_sources is provided by the Arcmap MCP server (pedralcg/arcmap-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 →