Get a list of backup and/or restore jobs for a connector
AI agents call get_job_history to retrieve information from Keepit MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical job information from the Keepit backup service. It performs a read-only operation that retrieves existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is limited to information disclosure about past jobs, which is low risk compared to tools that could modify backups or execute restore operations.
From the tool's definition Tool name is "get_job_history" and description states it retrieves "a list of backup and/or restore jobs". The verb "Get" and "list" indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get a list of backup and/or restore jobs for a connector. It is categorised as a Read tool in the Keepit MCP MCP Server, which means it retrieves data without modifying state.
Register the Keepit MCP server in PolicyLayer and add a rule for get_job_history: 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 Keepit MCP. Nothing to install.
get_job_history 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 get_job_history 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 get_job_history. 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.
get_job_history is provided by the Keepit MCP server (keepit-official/keepit-mcp). 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 →