18 tools. 6 can modify or destroy data without limits.
2 destructive tools with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry checked 07/07/2026 · full schemas captured for 17 of 18 tools
Running more than one server? Check your whole stack →
Full per-tool breakdown → Model it in the token calculator →
6 of Events's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Events, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"purchase_ticket_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"delete_event_preferences": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"create_event_calendar_file": {
"limits": [
{
"counter": "create_event_calendar_file_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"get_event": {
"limits": [
{
"counter": "get_event_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
Yes. The Events server exposes 1 financial tools including purchase_ticket_order. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
Yes. The Events server exposes 1 destructive tools including delete_event_preferences. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Events server has 4 write tools including create_event_calendar_file, create_event_preference_profile, record_event_feedback. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Events.
18 tools across 4 categories: Destructive, Execute, Read, Write. 12 are read-only. 6 can modify, create, or delete data.
Register the Events MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 18 Events tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
18 Events tools catalogued and risk-classified — across an index of 46,500+ MCP servers.
These policies come from Events's registry record.
The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →