schedule_task
A execute tool on the Agent Jail MCP server.
This record as markdown: /tools/agent-jail-mcp/schedule-task.md
What schedule_task does on Agent Jail
AI agents invoke schedule_task to trigger actions in Agent Jail. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why schedule_task is rated High
The name 'schedule_task' strongly suggests this tool schedules or triggers execution of tasks, placing it in the Execute category. However, with no description available, the exact behavior is unknown. Given the potential blast radius of scheduling arbitrary tasks (which could cause unintended operations), severity is rated high. Confidence is low due to the empty description.
From the tool's definition Tool name 'schedule_task' implies triggering or scheduling execution of some task; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs schedule_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Jail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For schedule_task, this is the rule to start with:
schedule_task stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Jail, apply this rule, and every schedule_task call is checked against it from then on.
Questions about schedule_task
schedule_task is a execute tool on the Agent Jail MCP server. It is categorised as a Execute tool in the Agent Jail MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agent Jail MCP server in PolicyLayer and add a rule for schedule_task: 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 Agent Jail. Nothing to install.
schedule_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the schedule_task 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 schedule_task. 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.
schedule_task is provided by the Agent Jail MCP server (idiscoord13-sketch/agent-jail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Jail, and thousands of servers like it.
Across the catalogue