memory_get_event | PolicyLayer

WHAT IT DOES

What memory_get_event does on Amazon Bedrock Knowledge Base Retrieval MCP Server

AI agents call memory_get_event to retrieve information from Amazon Bedrock Knowledge Base Retrieval MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why memory_get_event needs a policy

The 'get' verb combined with 'event' and 'memory' indicates this tool retrieves or queries stored event data without modifying it. This aligns with the Read category (retrieves data with no side effects). Severity is low because retrieval operations typically have limited blast radius unless the retrieved data itself is highly sensitive—though without a description this cannot be fully assessed.

From the tool's definition Tool name 'memory_get_event' suggests retrieval of event data from memory with 'get' indicating a read operation. The empty description limits confidence.

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

POLICY

How to control memory_get_event

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Bedrock Knowledge Base Retrieval MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_get_event:

policy.json

{
  "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.

Create a free account and register Amazon Bedrock Knowledge Base Retrieval MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Amazon Bedrock Knowledge Base Retrieval MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive cancel_logs_insight_query cancel_logs_insight_query Destructive delete delete Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime

All 805 Amazon Bedrock Knowledge Base Retrieval MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

Roll out MCP under one policy → Per-person scoped tokens, one central policy, and full audit across every server your team connects.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about memory_get_event

What does the memory_get_event tool do? +

memory_get_event. It is categorised as a Read tool in the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_get_event? +

Register the Amazon Bedrock Knowledge Base Retrieval MCP Server 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 Amazon Bedrock Knowledge Base Retrieval MCP Server. Nothing to install.

What risk level is memory_get_event? +

memory_get_event is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit memory_get_event? +

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.

How do I block memory_get_event completely? +

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.

What MCP server provides memory_get_event? +

memory_get_event is provided by the Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server (awslabs.bedrock-kb-retrieval-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 Amazon Bedrock Knowledge Base Retrieval MCP Server tool call.

Start from Amazon Bedrock Knowledge Base Retrieval MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

805 Amazon Bedrock Knowledge Base Retrieval MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.