This record as markdown: /tools/io-tinyfn-tinyfn/yes-no.md
What yes_no does on TinyFn
AI agents call yes_no 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 |
|---|---|---|---|
question | string | Yes | Your yes/no question |
Parameters from the server's own tool schema.
Why yes_no is rated Low
This is a pure read operation that returns a random binary response. It has no capability to modify data, execute code, delete resources, or commit financial obligations. The severity is low because misuse would only result in receiving a random answer, with minimal blast radius. The tool is deterministic in behavior (always returns yes or no) even if the selection is randomized.
From the tool's definition Tool description states 'Get a random yes or no answer' - this retrieves/generates a random value with no side effects, no state modifications, and no external operations triggered.
Attacks that exploit this kind of access
The rule that runs yes_no 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 yes_no, this is the rule to start with:
yes_no 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 yes_no call is checked against it from then on.
Questions about yes_no
Get a random yes or no answer. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
yes_no accepts 1 parameter: question. Required: question. 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 yes_no: 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.
yes_no 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 yes_no 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 yes_no. 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.
yes_no 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