AI agents call memory_get_event to retrieve information from Awslabs Amazon Sns Sqs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name pattern 'get_*' typically indicates a read operation that retrieves data without side effects. However, the empty description and non-standard naming (does not match SNS/SQS operations) reduce confidence. Absence of keywords like 'delete', 'send', 'create', or 'execute' suggests no destructive or execute capability. Classified as Read with low-to-medium confidence due to lack of descriptive information.
From the tool's definition Tool name 'memory_get_event' suggests retrieval of event data without modification. Description is empty, limiting confidence.
Documented attack patterns abuse exactly the kind of access memory_get_event 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_get_event:
{
"version": "1",
"default": "deny",
"tools": {
"memory_get_event": {}
}
}memory_get_event is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
memory_get_event. It is categorised as a Read tool in the Awslabs Amazon Sns Sqs MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Amazon Sns Sqs MCP server in PolicyLayer and add a rule for memory_get_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 Awslabs Amazon Sns Sqs. Nothing to install.
memory_get_event is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the memory_get_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.
Set action: deny in the PolicyLayer policy for memory_get_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.
memory_get_event 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.