Critical Risk →

cancel_logs_insight_query

Cancel in-progress CloudWatch queries

Risk signalsTerminates running queries

Part of the AWS server.

cancel_logs_insight_query can permanently delete data in AWS, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AWS →

Free to start. No card required.

AI agents may call cancel_logs_insight_query to permanently remove or destroy resources in AWS. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call cancel_logs_insight_query in a loop, permanently destroying resources in AWS. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cancel_logs_insight_query"
  ]
}

See the full AWS policy for all 58 tools.

Get this rule live on your own AWS server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AWS →

View all 58 tools →

These attack patterns abuse exactly the kind of access cancel_logs_insight_query gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cancel_logs_insight_query only ever does what you allow.

SECURE AWS →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the cancel_logs_insight_query tool do? +

Cancel in-progress CloudWatch queries. It is categorised as a Destructive tool in the AWS 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 cancel_logs_insight_query? +

Register the AWS MCP server in PolicyLayer and add a rule for cancel_logs_insight_query: 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 AWS. Nothing to install.

What risk level is cancel_logs_insight_query? +

cancel_logs_insight_query 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 cancel_logs_insight_query? +

Yes. Add a rate_limit block to the cancel_logs_insight_query 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 cancel_logs_insight_query completely? +

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

cancel_logs_insight_query is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS tool call.

Deterministic rules across all 58 AWS tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.