8 tools. 5 can modify or destroy data without limits.
5 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (opsgenie_acknowledge_alert, opsgenie_add_details, opsgenie_add_note) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
opsgenie_acknowledge_alert:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
opsgenie_list_alert_logs:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Opsgenie Alert Management Server server has 5 write tools including opsgenie_acknowledge_alert, opsgenie_add_details, opsgenie_add_note. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
8 tools across 2 categories: Read, Write. 3 are read-only. 5 can modify, create, or delete data.
One line change. Instead of running the Opsgenie Alert Management Server server directly, prefix it with Intercept: intercept -c burakdirin-opsgenie-mcp-server.yaml -- npx -y @burakdirin/opsgenie-mcp-server. Download a pre-built policy from policylayer.com/policies/burakdirin-opsgenie-mcp-server and adjust the limits to match your use case.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.