This record as markdown: /tools/io-tinyfn-tinyfn/is-leap-year.md
What is_leap_year does on TinyFn
AI agents call is_leap_year to retrieve information from TinyFn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
year | integer | Yes | Year to check |
Parameters from the server's own tool schema.
Why is_leap_year is rated Low
This is a deterministic, read-only utility function that checks a property of a year value and returns a result. It has no capability to modify, delete, execute code, trigger external services, or affect financial systems. The low severity reflects the benign nature of the operation—misuse of this tool poses minimal risk to systems or data.
From the tool's definition Tool name 'is_leap_year' and description 'Check if a year is a leap year' indicate a pure query operation that retrieves or computes a boolean value about a calendar property with no side effects, no data modification, and no external operations triggered.
Attacks that exploit this kind of access
The rule that runs is_leap_year safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TinyFn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For is_leap_year, this is the rule to start with:
is_leap_year is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TinyFn, apply this rule, and every is_leap_year call is checked against it from then on.
Questions about is_leap_year
Check if a year is a leap year. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
is_leap_year accepts 1 parameter: year. Required: year. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn MCP server in PolicyLayer and add a rule for is_leap_year: 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 TinyFn. Nothing to install.
is_leap_year 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 is_leap_year 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 is_leap_year. 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.
is_leap_year is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TinyFn, and thousands of servers like it.
This server
Across the catalogue