Medium Risk

mark_processed

Mark a webhook event as processed so it won't appear again.

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

github-webhook-mcp Write Risk 2/5

AI agents use mark_processed to create or modify resources in Github Webhook. 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 mark_processed 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 Github Webhook.

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

io-github-liplus-project-github-webhook-mcp.yaml
tools:
  mark_processed:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Github Webhook policy for all 5 tools.

Tool Name mark_processed
Category Write
Risk Level Medium

Agents calling write-class tools like mark_processed 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 mark_processed tool do? +

Mark a webhook event as processed so it won't appear again.. It is categorised as a Write tool in the Github Webhook 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_processed? +

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

What risk level is mark_processed? +

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

Can I rate-limit mark_processed? +

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

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

mark_processed is provided by the Github Webhook MCP server (github-webhook-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Github Webhook

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.