AI agents call jasper_delete_job to permanently remove resources in Jasperreports — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a scheduled job from JasperReports Server. Job deletion cannot be undone without restoration from backups. While the blast radius is somewhat contained (affects scheduling, not data itself), the irreversible nature of deletion and potential business impact (loss of automated reporting workflows) places it in the Destructive category, which is more severe than Execute or Write.
From the tool's definition Tool name and description: 'jasper_delete_job' that performs 'Delete a scheduled job'. The verb 'Delete' combined with 'job' indicates irreversible removal of a scheduled task.
Documented attack patterns abuse exactly the kind of access jasper_delete_job gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jasperreports, and nothing reaches the server without passing your rules. This is the rule we recommend for jasper_delete_job:
{
"version": "1",
"default": "deny",
"hide": [
"jasper_delete_job"
]
} jasper_delete_job disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a scheduled job. It is categorised as a Destructive tool in the Jasperreports MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Jasperreports MCP server in PolicyLayer and add a rule for jasper_delete_job: 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 Jasperreports. Nothing to install.
jasper_delete_job is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the jasper_delete_job 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 jasper_delete_job. 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.
jasper_delete_job is provided by the Jasperreports MCP server (mr-wolf-gb/jasperreports-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jasperreports, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Jasperreports tools catalogued and risk-classified — across an index of 43,000+ MCP servers.