List all AAP controller and execution node instances.
AI agents call aap_list_instances to retrieve information from AAP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a simple enumeration of existing infrastructure instances without modifying, executing, or deleting anything. This is a pure information-gathering operation. While the list of instances could be sensitive in some contexts, the tool itself performs no write, execute, or destructive actions. Severity is low because it only reads existing data.
From the tool's definition Tool name 'aap_list_instances' and description 'List all AAP controller and execution node instances' indicate a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
List all AAP controller and execution node instances. It is categorised as a Read tool in the AAP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AAP MCP Server MCP server in PolicyLayer and add a rule for aap_list_instances: 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 AAP MCP Server. Nothing to install.
aap_list_instances 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 aap_list_instances 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 aap_list_instances. 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.
aap_list_instances is provided by the AAP MCP Server MCP server (srinivassrinu842/aap-mcp-server). 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 →