Medium Risk

create_event

Create a conversion event for a contact

How to control create_event ↓

What create_event does on Mcp Ap2

AI agents use create_event to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.

Medium Risk

Why create_event needs a policy

This tool creates a new event record tied to a contact. While 'conversion event' in a payment protocol context could influence financial workflows, the tool itself is creating/recording an event (reversible data modification) rather than moving money or executing arbitrary code. Classified as Write (creates data).

From the tool's definition Tool name 'create_event' and description 'Create a conversion event for a contact' indicate data creation; server context (AP2 — Google's Agent-to-Agent Payment Protocol) suggests financial/e-commerce domain where conversion events drive billing or…

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

How to control create_event

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for create_event:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_event": {
      "limits": [
        {
          "counter": "create_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

create_event stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_event

What does the create_event tool do? +

Create a conversion event for a contact. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_event? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for create_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 Mcp Ap2. Nothing to install.

What risk level is create_event? +

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

Can I rate-limit create_event? +

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

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

create_event is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, 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.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.