This record as markdown: /tools/io-tinyfn-tinyfn/week-number-2.md
What week_number_2 does on TinyFn
AI agents call week_number_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 |
|---|---|---|---|
datetime_str | string | Yes | Datetime in ISO format |
Parameters from the server's own tool schema.
Why week_number_2 is rated Low
This tool performs a deterministic read-only computation on a date input to return its ISO week number. It retrieves information without creating, modifying, deleting, or executing any operations. No data is changed, no code is executed, and no side effects occur. This is a straightforward Read classification with low severity due to its purely informational nature.
From the tool's definition Tool name 'week_number_2' and description 'Get the ISO week number for a date' indicate a pure query operation that retrieves date information without side effects.
Attacks that exploit this kind of access
The rule that runs week_number_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 week_number_2, this is the rule to start with:
week_number_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 week_number_2 call is checked against it from then on.
Questions about week_number_2
Get the ISO week number for a date. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
week_number_2 accepts 1 parameter: datetime_str. Required: datetime_str. 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 week_number_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.
week_number_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 week_number_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 week_number_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.
week_number_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