memory_delete_event

memory_delete_event

Server AWS IoT SiteWise MCP Server awslabs.aws-iot-sitewise-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What memory_delete_event does on AWS IoT SiteWise MCP Server

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

Why memory_delete_event needs a policy

The 'delete' verb in the tool name places this in the Destructive category, as deletion operations cannot be undone. While the empty description reduces confidence slightly, the explicit use of 'delete' in the name is a clear signal of destructive capability. Severity is high because unauthorized deletion of events could cause data loss and operational disruption in an AWS IoT SiteWise context.

From the tool's definition Tool name 'memory_delete_event' contains the verb 'delete', which indicates irreversible removal of data. No description provided, but the name strongly suggests permanent deletion of an event from memory or storage.

Questions about memory_delete_event

What does the memory_delete_event tool do? +

memory_delete_event. It is categorised as a Destructive tool in the AWS IoT SiteWise 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_event? +

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

What risk level is memory_delete_event? +

memory_delete_event 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_event? +

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

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

memory_delete_event is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.