Lists recent backup jobs, optionally filtering by state (default: FAILED).
AI agents call list_backup_jobs to retrieve information from AWS 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 and filters existing backup job metadata without side effects. It is a passive read operation that queries AWS Backup service state. The low severity reflects minimal blast radius—an AI agent misusing this tool could only over-query or retrieve unintended job metadata, not alter infrastructure or cause financial impact.
From the tool's definition Tool name 'list_backup_jobs' and description 'Lists recent backup jobs' indicate a query/retrieval operation with optional filtering by state.
Attacks that exploit this kind of access
Lists recent backup jobs, optionally filtering by state (default: FAILED). It is categorised as a Read tool in the AWS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for list_backup_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 AWS MCP Server. Nothing to install.
list_backup_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_backup_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_backup_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_backup_jobs is provided by the AWS MCP Server MCP server (sergiosediq/aws-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 →