getEventDetails

THE RISK

Low Risk

Why getEventDetails needs a policy

This tool retrieves and queries event data without creating, modifying, deleting, executing code, or affecting financial operations. It is a straightforward data read operation with minimal risk if misused by an AI agent.

From the tool's definition Tool name 'getEventDetails' and description 'Get detailed information for a specific event' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access getEventDetails gives an agent:

POLICY

How to control getEventDetails

PolicyLayer is an MCP gateway — it sits between your AI agents and Intervals Icu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getEventDetails:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getEventDetails": {}
  }
}

getEventDetails is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Intervals Icu MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Intervals Icu MCP Server tools

Destructive deleteBulkEvents Delete multiple events from the athlete Destructive deleteEvent Delete an event for the current athlete by event ID. Write createBulkEvents Create multiple events for the current athlete in bulk. Uses the same schema as createEven Write createEvent Create an event for the current athlete, optionally including intervals in the Native Inte Read getActivities Get a list of activities for an athlete from Intervals.icu. Read getActivityDetails Get detailed information for a specific activity from Intervals.icu. Read getAthleteDetails Get athlete details. Read getEvents Get a list of events for an athlete from Intervals.icu.

All 10 Intervals Icu MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about getEventDetails

What does the getEventDetails tool do? +

Get detailed information for a specific event from Intervals.icu. It is categorised as a Read tool in the Intervals Icu MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getEventDetails? +

Register the Intervals Icu MCP Server MCP server in PolicyLayer and add a rule for getEventDetails: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Intervals Icu MCP Server. Nothing to install.

What risk level is getEventDetails? +

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

Can I rate-limit getEventDetails? +

Yes. Add a rate_limit block to the getEventDetails rule in your PolicyLayer 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 getEventDetails completely? +

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

getEventDetails is provided by the Intervals Icu MCP Server MCP server (mrgeorgegray/intervals-icu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Intervals Icu MCP Server tool call.

Start from Intervals Icu MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →