Medium Risk

memory_create_event

Create an event in an AgentCore Memory resource (short-term memory). COST WARNING: Creating events triggers background long-term memory extraction if strategies are configured. This consumes compute resources and incurs AWS charges. Events represent interactions (messages, tool calls) within a ...

Accepts raw HTML/template content (payload)

Part of the AWS Bedrock AgentCore MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use memory_create_event to create or modify resources in AWS Bedrock AgentCore MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call memory_create_event repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AWS Bedrock AgentCore MCP Server.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

aws-bedrock-agentcore-mcp-server.yaml
tools:
  memory_create_event:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.

Tool Name memory_create_event
Category Write
Risk Level Medium

View all 122 tools →

Agents calling write-class tools like memory_create_event have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the memory_create_event tool do? +

Create an event in an AgentCore Memory resource (short-term memory). COST WARNING: Creating events triggers background long-term memory extraction if strategies are configured. This consumes compute resources and incurs AWS charges. Events represent interactions (messages, tool calls) within a session. They are immutable and timestamped.. It is categorised as a Write tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_create_event? +

Add a rule in your Intercept YAML policy under the tools section for memory_create_event. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Bedrock AgentCore MCP Server MCP server.

What risk level is memory_create_event? +

memory_create_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_create_event? +

Yes. Add a rate_limit block to the memory_create_event rule in your Intercept 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_create_event completely? +

Set action: deny in the Intercept policy for memory_create_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_create_event? +

memory_create_event is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.