util_is_leap_year
Delx first-party micro-utility util_is_leap_year at $0.001 USDC.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-is-leap-year.md
What util_is_leap_year does on Delx Mcp A2a
AI agents call util_is_leap_year to retrieve information from Delx Mcp A2a 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 |
Parameters from the server's own tool schema.
Why util_is_leap_year is rated Low
This is a pure computational utility that reads/queries a mathematical property of a calendar year. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary commands or transfer funds. The $0.001 USDC pricing is a usage fee, not a financial transaction by the tool itself.
From the tool's definition Tool name 'util_is_leap_year' and description 'micro-utility' indicate a simple query function that determines whether a given year is a leap year.
Attacks that exploit this kind of access
The rule that runs util_is_leap_year safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_is_leap_year, this is the rule to start with:
util_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 Delx Mcp A2a, apply this rule, and every util_is_leap_year call is checked against it from then on.
Questions about util_is_leap_year
Delx first-party micro-utility util_is_leap_year at $0.001 USDC. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_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 Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_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 Delx Mcp A2a. Nothing to install.
util_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 util_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 util_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.
util_is_leap_year is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue