memory_batch_delete_records

memory_batch_delete_records

Server Amazon SageMaker AI MCP Server awslabs.sagemaker-ai-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What memory_batch_delete_records does on Amazon SageMaker AI MCP Server

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

Why memory_batch_delete_records needs a policy

The tool name explicitly indicates deletion of records in batch mode. Deletion is irreversible and cannot be undone, making this a Destructive action. Although the description is empty, the naming convention is sufficiently clear. The batch nature of the operation elevates the potential impact. High severity is assigned due to the risk of mass data loss if an AI agent misuses this tool with incorrect parameters.

From the tool's definition Tool name 'memory_batch_delete_records' contains 'delete' and 'batch', indicating irreversible deletion of multiple records. The 'batch' qualifier suggests bulk operations with potentially large blast radius.

Questions about memory_batch_delete_records

What does the memory_batch_delete_records tool do? +

memory_batch_delete_records. It is categorised as a Destructive tool in the Amazon SageMaker AI 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_batch_delete_records? +

Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for memory_batch_delete_records: 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 Amazon SageMaker AI MCP Server. Nothing to install.

What risk level is memory_batch_delete_records? +

memory_batch_delete_records 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_batch_delete_records? +

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

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

memory_batch_delete_records is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-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.