convert_timestamp · TinyFn MCP: Risk & Policy

WHAT IT DOES

What convert_timestamp does on TinyFn

AI agents use convert_timestamp to create or update resources in TinyFn — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TinyFn environment.

PARAMETERS

Parameter	Type	Required	Description
`timestamp`	integer	Yes	Unix timestamp (seconds)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why convert_timestamp needs a policy

An AI agent can call convert_timestamp faster than any human can review — one bad instruction and it creates or modifies resources in TinyFn by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_timestamp Rate-limited

convert_timestamp stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "convert_timestamp": {
      "limits": [
        {
          "counter": "convert_timestamp_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TinyFn, so you can run agents against it safely.

FAQ

Questions about convert_timestamp

What does the convert_timestamp tool do? +

Convert Unix timestamp to date. It is categorised as a Write tool in the TinyFn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does convert_timestamp accept? +

convert_timestamp accepts 1 parameter: timestamp. Required: timestamp. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on convert_timestamp? +

Register the TinyFn MCP server in PolicyLayer and add a rule for convert_timestamp: 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.

What risk level is convert_timestamp? +

convert_timestamp is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit convert_timestamp? +

Yes. Add a rate_limit block to the convert_timestamp 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.

How do I block convert_timestamp completely? +

Set action: deny in the PolicyLayer policy for convert_timestamp. 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.

What MCP server provides convert_timestamp? +

convert_timestamp 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.

// THE FULL RECORD

convert_timestamp is one line of TinyFn's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →