delete_schedule

THE RISK

Critical Risk

Why delete_schedule needs a policy

Deletion operations fall into the Destructive category as they irreversibly remove data or configurations. Within a CloudWatch/AWS context, deleting a schedule could affect monitoring, alerts, or automation workflows. While the blast radius is significant (high severity), confidence is moderate due to the absence of a descriptive field that would clarify the scope and impact of this deletion.

From the tool's definition Tool name 'delete_schedule' indicates irreversible deletion of a schedule resource. The empty description prevents full certainty, but the 'delete' verb strongly suggests data removal that cannot be undone.

Documented attack patterns abuse exactly the kind of access delete_schedule gives an agent:

POLICY

How to control delete_schedule

PolicyLayer is an MCP gateway — it sits between your AI agents and CloudWatch Application Signals MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_schedule:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_schedule"
  ]
}

delete_schedule disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register CloudWatch Application Signals MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CloudWatch Application Signals MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint

All 805 CloudWatch Application Signals MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in CloudWatch Application Signals MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_schedule

What does the delete_schedule tool do? +

delete_schedule. It is categorised as a Destructive tool in the CloudWatch Application Signals MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_schedule? +

Register the CloudWatch Application Signals MCP Server MCP server in PolicyLayer and add a rule for delete_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 CloudWatch Application Signals MCP Server. Nothing to install.

What risk level is delete_schedule? +

delete_schedule is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_schedule? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_schedule completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_schedule? +

delete_schedule is provided by the CloudWatch Application Signals MCP Server MCP server (awslabs.cloudwatch-applicationsignals-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CloudWatch Application Signals MCP Server tool call.

Start from CloudWatch Application Signals MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →