AI agents call get_today_json 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 position among other read-only retrieval tools (get_availability, get_event, get_events_in_range) indicate this retrieves calendar data for today in JSON format. This is a read-only query with no side effects. Confidence is slightly reduced due to empty description, but sibling tool patterns provide strong contextual evidence.
From the tool's definition Tool name 'get_today_json' with 'get_' prefix and sibling tools like 'get_availability', 'get_calendars', 'get_event' that are clearly retrieval operations. No description provided, but naming convention and context strongly suggest data retrieval.
Documented attack patterns abuse exactly the kind of access get_today_json 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_today_json:
{
"version": "1",
"default": "deny",
"tools": {
"get_today_json": {}
}
}get_today_json 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_today_json. 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_today_json: 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_today_json 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_today_json 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_today_json. 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_today_json 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.