AI agents call memory_delete_record to permanently remove resources in Awslabs Amazon Sns Sqs — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name explicitly contains 'delete', which falls under the Destructive category as it removes data that cannot be undone. Although the description is empty and context suggests this is from a messaging/SNS/SQS server (making 'memory' semantics unclear), the delete operation is inherently destructive. High severity assigned because deletion operations can cause significant data loss if misused by an AI agent.
From the tool's definition Tool name 'memory_delete_record' contains 'delete', which indicates irreversible data removal. Description is empty, limiting certainty but the semantic meaning of 'delete' in the tool name is clear.
Documented attack patterns abuse exactly the kind of access memory_delete_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awslabs Amazon Sns Sqs, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_delete_record:
{
"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.
Free to start. No card required.
memory_delete_record. It is categorised as a Destructive tool in the Awslabs Amazon Sns Sqs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Awslabs Amazon Sns Sqs 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 Awslabs Amazon Sns Sqs. Nothing to install.
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.
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.
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.
memory_delete_record is provided by the Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awslabs Amazon Sns Sqs, 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 Awslabs Amazon Sns Sqs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.