AI agents call list_layout_elements 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 tool name contains the verb 'list', which is a classic Read operation pattern. Given the ArcMap context and sibling tools that clearly perform queries (describe_data, count_features), this tool almost certainly retrieves or enumerates layout elements without side effects. The empty description reduces confidence slightly, but the naming convention and server context are strong indicators of Read semantics.
From the tool's definition Tool name 'list_layout_elements' indicates retrieval of layout elements from ArcMap; no description provided, but naming and context (alongside other read-only tools like 'describe_data' and 'count_features') suggest data querying rather than modification.
Attacks that exploit this kind of access
list_layout_elements. 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_layout_elements: 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_layout_elements 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_layout_elements 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_layout_elements. 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_layout_elements 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 →