This record as markdown: /tools/io-tinyfn-tinyfn/is-leap-year-2.md
What is_leap_year_2 does on TinyFn
AI agents call is_leap_year_2 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_2 is rated Low
This is a deterministic utility function that performs a read-only check on calendar data. It takes a year as input and returns a boolean result indicating leap year status. There is no data modification, deletion, execution of arbitrary code, financial impact, or destructive capability. It belongs in the Read category with low severity since misuse poses no significant risk.
From the tool's definition Tool name 'is_leap_year_2' and description 'Check if a year is a leap year' indicate a pure query operation that retrieves or validates information about a given year without any side effects, modifications, or external actions.
Attacks that exploit this kind of access
The rule that runs is_leap_year_2 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_2, this is the rule to start with:
is_leap_year_2 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_2 call is checked against it from then on.
Questions about is_leap_year_2
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_2 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_2: 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_2 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_2 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_2. 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_2 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