Ignore a calendar event so it won't show as a conflict when checking poll time slots. Use seriesWide=true to ignore all instances of a recurring event, or false to ignore only a specific instance. Requires authentication via per-call oauthToken/apiKey, or pre-configured via --oauth-token/--api-ke...
Handles credentials or secrets (apiKey); Single-target operation
Part of the Timergy MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call ignore_event to retrieve information from Timergy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though ignore_event only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
ignore_event:
rules:
- action: allowSee the full Timergy policy for all 22 tools.
Ignore a calendar event so it won't show as a conflict when checking poll time slots. Use seriesWide=true to ignore all instances of a recurring event, or false to ignore only a specific instance. Requires authentication via per-call oauthToken/apiKey, or pre-configured via --oauth-token/--api-key CLI flags. Get the eventId, connectionId, and provider from check_conflicts results.. It is categorised as a Read tool in the Timergy MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for ignore_event. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Timergy MCP server.
ignore_event is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ignore_event 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.
Set action: deny in the Intercept policy for ignore_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.
ignore_event is provided by the Timergy MCP server (@timergy/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept