AI agents call list_ddp 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.
The 'list' verb strongly suggests a retrieval operation with no side effects. Even without a detailed description, the naming pattern and server context indicate this tool queries or enumerates DDP objects rather than creating, modifying, deleting, or executing code. Confidence is slightly reduced due to the empty description, but the semantic evidence is clear.
From the tool's definition Tool name 'list_ddp' indicates listing/querying operation; 'list' prefix is a Read category indicator. Description is empty, but context from sibling tools (add_layer, apply_symbology_from_layer, etc.) and server purpose (ArcMap control) suggest this…
Attacks that exploit this kind of access
list_ddp. 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_ddp: 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_ddp 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_ddp 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_ddp. 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_ddp 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 →