ss_clear_schedule
A destructive tool on the Ultra MCP-SS MCP server.
This record as markdown: /tools/motebus-ultra-mcp-ss/ss-clear-schedule.md
What ss_clear_schedule does on Ultra MCP-SS
AI agents call ss_clear_schedule to permanently remove resources in Ultra MCP-SS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why ss_clear_schedule is rated Critical
An AI agent that decides to call ss_clear_schedule doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ultra MCP-SS is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs ss_clear_schedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ultra MCP-SS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ss_clear_schedule, this is the rule to start with:
ss_clear_schedule is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ultra MCP-SS, apply this rule, and every ss_clear_schedule call is checked against it from then on.
Questions about ss_clear_schedule
ss_clear_schedule is a destructive tool on the Ultra MCP-SS MCP server. It is categorised as a Destructive tool in the Ultra MCP-SS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ultra MCP-SS MCP server in PolicyLayer and add a rule for ss_clear_schedule: 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 Ultra MCP-SS. Nothing to install.
ss_clear_schedule 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 ss_clear_schedule 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 ss_clear_schedule. 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.
ss_clear_schedule is provided by the Ultra MCP-SS MCP server (motebus/ultra-mcp-ss). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ultra MCP-SS, and thousands of servers like it.
Across the catalogue