AI agents call list_failed_jobs to retrieve information from Ppdm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical backup job status information for monitoring and diagnostic purposes. It performs a read-only query of existing backup job data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could only gain visibility into backup failure history, not alter infrastructure or data.
From the tool's definition Tool description states 'List failed backup jobs from PPDM. Returns asset name, type, error, and start time.' The verb 'List' and the return-only nature (asset name, type, error, start time) indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
List failed backup jobs from PPDM. Returns asset name, type, error, and start time. It is categorised as a Read tool in the Ppdm MCP Server, which means it retrieves data without modifying state.
Register the Ppdm MCP server in PolicyLayer and add a rule for list_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 Ppdm. Nothing to install.
list_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 list_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 list_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.
list_failed_jobs is provided by the Ppdm MCP server (moodswing9/ppdm-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 →