check_conflicts

Check which poll time slots conflict with the creator's calendar events. Requires authentication via per-call oauthToken/apiKey, or pre-configured via --oauth-token/--api-key CLI flags. Returns each option with conflict status and conflicting event names. Use this to help the creator avoid double...

Handles credentials or secrets (apiKey)

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

@timergy/mcp Read Risk 2/5

// WHEN AI AGENTS USE THIS TOOL

AI agents call check_conflicts 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.

// WHY ENFORCE A POLICY ON CHECK_CONFLICTS

Even though check_conflicts 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.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

timergy.yaml

tools:
  check_conflicts:
    rules:
      - action: allow

See the full Timergy policy for all 22 tools.

// DETAILS

Tool Name check_conflicts

Category Read

MCP Server Timergy MCP Server

Risk Level Low

// MORE TIMERGY TOOLS

Financial auto_finalize Destructive delete_poll Destructive delete_webhook Execute suggest_best_option Write create_poll Write create_survey Write create_webhook Write invite_to_poll

View all 22 tools →

// RELATED READING

// FAQ

What does the check_conflicts tool do? +

How do I enforce a policy on check_conflicts? +

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

What risk level is check_conflicts? +

check_conflicts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_conflicts? +

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

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

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

check_conflicts

Enforce policies on Timergy