aap_get_failed_jobs
AI agents call aap_get_failed_jobs 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 retrieves historical job failure data from Ansible Automation Platform. It performs a query operation with no side effects—no data is created, modified, deleted, or external operations triggered. The blast radius is minimal as misuse would only expose existing job information. Although the description is empty (lowering confidence slightly), the naming convention strongly indicates read-only behavior.
From the tool's definition Tool name 'aap_get_failed_jobs' indicates a retrieval operation that queries job status without modifying state. The 'get_' prefix and absence of mutation verbs (create, delete, update, cancel) confirm read-only behavior.
Attacks that exploit this kind of access
aap_get_failed_jobs. 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_failed_jobs: 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_failed_jobs 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_failed_jobs 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_failed_jobs. 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_failed_jobs 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 →