log-event-to-bus · Mmc MCP: Risk & Policy

WHAT IT DOES

What log-event-to-bus does on Mmc

AI agents use log-event-to-bus to create or update resources in Mmc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mmc environment.

WHY IT NEEDS A POLICY

Why log-event-to-bus needs a policy

This tool writes data to an event store by logging custom events. It creates new records in the system, which is a reversible write operation. The severity is medium because injecting arbitrary events into a workflow event bus could potentially disrupt or manipulate process sequencing, but it does not directly delete data or execute code.

From the tool's definition 'Log a custom event into the event store' and 'record observations, decisions, or notable moments during a workflow instance'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log-event-to-bus Rate-limited

log-event-to-bus 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log-event-to-bus": {
      "limits": [
        {
          "counter": "log-event-to-bus_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mmc, so you can run agents against it safely.

FAQ

Questions about log-event-to-bus

What does the log-event-to-bus tool do? +

Log a custom event into the event store. Use this to record observations, decisions, or notable moments during a workflow instance. Pass the. It is categorised as a Write tool in the Mmc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log-event-to-bus? +

Register the Mmc MCP server in PolicyLayer and add a rule for log-event-to-bus: 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 Mmc. Nothing to install.

What risk level is log-event-to-bus? +

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

Can I rate-limit log-event-to-bus? +

Yes. Add a rate_limit block to the log-event-to-bus 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 log-event-to-bus completely? +

Set action: deny in the PolicyLayer policy for log-event-to-bus. 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 log-event-to-bus? +

log-event-to-bus is provided by the Mmc MCP server (modelmycontext/mmc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.