Critical Risk →

memory_delete_record

memory_delete_record

How to control memory_delete_record ↓

What memory_delete_record does on AWS Labs CloudTrail MCP Server

AI agents call memory_delete_record to permanently remove resources in AWS Labs CloudTrail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why memory_delete_record needs a policy

Despite the empty description, the name explicitly contains 'delete', placing this tool in the Destructive category. Without clarification on scope, this is treated as a data deletion operation. The high severity reflects potential loss of audit or operational records in a CloudTrail context, though confidence is reduced slightly due to lack of descriptive detail.

From the tool's definition Tool name 'memory_delete_record' contains 'delete', which indicates irreversible removal of data.

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

How to control memory_delete_record

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs CloudTrail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_delete_record:

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

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

  1. Create a free account and register AWS Labs CloudTrail MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_delete_record

What does the memory_delete_record tool do? +

memory_delete_record. It is categorised as a Destructive tool in the AWS Labs CloudTrail 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 memory_delete_record? +

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

What risk level is memory_delete_record? +

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

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

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

memory_delete_record is provided by the AWS Labs CloudTrail MCP Server MCP server (awslabs.cloudtrail-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 AWS Labs CloudTrail MCP Server tool call.

Start from AWS Labs CloudTrail MCP Server, 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.

805 AWS Labs CloudTrail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.