report_event · QuickContract MCP: Risk & Policy

WHAT IT DOES

What report_event does on QuickContract MCP

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

WHY IT NEEDS A POLICY

Why report_event needs a policy

Reporting a signed event modifies the state of a contract by appending or recording a signed event, which is a write operation. However, on a blockchain/escrow platform like QuickContract, recording signed events can have significant downstream consequences (e.g., triggering obligations, releasing escrow, advancing contract state), elevating severity to high.

From the tool's definition "Report a signed event to a contract" — writes a signed event record to an existing contract

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

report_event Rate-limited

report_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "report_event": {
      "limits": [
        {
          "counter": "report_event_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 QuickContract MCP, so you can run agents against it safely.

FAQ

Questions about report_event

What does the report_event tool do? +

Report a signed event to a contract\. It is categorised as a Write tool in the QuickContract MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on report_event? +

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

What risk level is report_event? +

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

Can I rate-limit report_event? +

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

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

report_event is provided by the QuickContract MCP server (quickcontractio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.