AI agents call sign to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
number | number | Yes | Number to check |
Parameters from the server's own tool schema.
This is a deterministic mathematical utility that queries a property of its input and returns a result. It matches the Read category pattern: it retrieves/computes information without modifying state, creating resources, executing arbitrary code, or causing destructive changes. The minimal severity reflects that misuse cannot harm systems, data, or operations.
From the tool's definition Tool 'sign' retrieves and returns the mathematical sign of a number (-1, 0, or 1). This is a pure computational function with no side effects, data modification, or external operations.
Attacks that exploit this kind of access
Get the sign of a number (-1, 0, or 1). It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
sign accepts 1 parameter: number. Required: number. 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 sign: 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.
sign 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 sign 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 sign. 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.
sign 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.
sign 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 →