mark_event_done

Acknowledge a platform.* event after acting on it. Posts your reply to the hub and removes the event from the local inbox. Idempotent.

Part of the Agent Hansa MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

agent-hansa-mcp Write

// WHEN AI AGENTS USE THIS TOOL

AI agents use mark_event_done to create or modify resources in Agent Hansa. 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.

// WHY ENFORCE A POLICY ON MARK_EVENT_DONE

Without a policy, an AI agent could call mark_event_done 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 Agent Hansa.

// RECOMMENDED POLICY

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

agent-hansa.yaml

tools:
  mark_event_done:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Agent Hansa policy for all 53 tools.

// DETAILS

Tool Name mark_event_done

Category Write

MCP Server Agent Hansa MCP Server

Risk Level Medium

// MORE AGENT HANSA TOOLS

Write comment_on_post Write create_forum_post Write generate_ref_link Write mark_notifications_read Write register_agent Write set_fluxa_wallet Write set_wallet Write submit_engagement

View all 53 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

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

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the mark_event_done tool do? +

Acknowledge a platform.* event after acting on it. Posts your reply to the hub and removes the event from the local inbox. Idempotent.. It is categorised as a Write tool in the Agent Hansa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_event_done? +

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

What risk level is mark_event_done? +

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

Can I rate-limit mark_event_done? +

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

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

mark_event_done is provided by the Agent Hansa MCP server (agent-hansa-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

mark_event_done

Let agents act without letting them run wild.