AI agents call fizzbuzz 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 |
|---|---|---|---|
n | integer | Yes | Number to check |
Parameters from the server's own tool schema.
FizzBuzz is a purely deterministic function that computes and returns a value (Fizz, Buzz, FizzBuzz, or the number). It reads/computes only, with no writes, execution of external commands, or destructive operations. The server description confirms these are '500+ deterministic tools' for math and conversion, reinforcing a Read/compute classification. Severity is low as misuse has essentially zero blast radius.
From the tool's definition 'The classic FizzBuzz' — a deterministic computation that returns FizzBuzz output for a given number; no side effects, no data modification
Attacks that exploit this kind of access
The classic FizzBuzz. Enterprise-grade. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
fizzbuzz accepts 1 parameter: n. Required: n. 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 fizzbuzz: 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.
fizzbuzz 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 fizzbuzz 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 fizzbuzz. 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.
fizzbuzz 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.
fizzbuzz 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 →