AI agents call get_recurring to retrieve information from Fantastical MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context of sibling read-only tools strongly suggest this retrieves recurring calendar event data without modification. Empty description lowers confidence slightly, but the consistent naming pattern and server's stated capability to 'read and create' events (with separate tools for each action) indicates this is a read operation. No side effects expected.
From the tool's definition Tool name 'get_recurring' with empty description; sibling tools show pattern of read-only operations (get_availability, get_calendars, get_event, get_events_by_calendar, get_events_in_range, get_invitations, get_recent, get_today); name prefix 'get_'…
Documented attack patterns abuse exactly the kind of access get_recurring gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fantastical MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_recurring:
{
"version": "1",
"default": "deny",
"tools": {
"get_recurring": {}
}
}get_recurring is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_recurring. It is categorised as a Read tool in the Fantastical MCP MCP Server, which means it retrieves data without modifying state.
Register the Fantastical MCP server in PolicyLayer and add a rule for get_recurring: 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 Fantastical MCP. Nothing to install.
get_recurring 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 get_recurring 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.
Set action: deny in the PolicyLayer policy for get_recurring. 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.
get_recurring is provided by the Fantastical MCP server (jaydenk/fantastical-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fantastical MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Fantastical MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.