Check AAP Controller health status (ping endpoint).
AI agents call aap_get_controller_health 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.
This tool performs a read-only health check operation. It queries the controller's status without side effects, no code execution, no data modification, and no resource changes. The ping endpoint is a standard diagnostic operation with minimal blast radius if misused—at worst, an agent could repeatedly call it to monitor or map the system, but no harmful outcomes result from its execution.
From the tool's definition Tool name and description explicitly indicate a health check via ping endpoint: 'Check AAP Controller health status (ping endpoint)'.
Attacks that exploit this kind of access
Check AAP Controller health status (ping endpoint). 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_get_controller_health: 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_get_controller_health 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_get_controller_health 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_get_controller_health. 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_get_controller_health 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 →