yesno_random
Get a random yes/no answer with an animated GIF.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/yesno-random.md
What yesno_random does on UnClick
AI agents call yesno_random to retrieve information from UnClick 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 |
|---|---|---|---|
force | string | — | Force a specific answer |
Parameters from the server's own tool schema.
Why yesno_random is rated Low
This tool only fetches and returns data (a random boolean answer and a GIF). It has no side effects, does not modify any state, and does not execute commands or perform financial transactions. It is purely informational retrieval, fitting the Read category with low severity due to the absence of any operational or security impact.
From the tool's definition Tool 'yesno_random' retrieves a random yes/no answer and an animated GIF. No modification, deletion, or execution of external operations occurs. The description indicates a read-only retrieval of randomized data.
Attacks that exploit this kind of access
The rule that runs yesno_random safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For yesno_random, this is the rule to start with:
yesno_random 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 UnClick, apply this rule, and every yesno_random call is checked against it from then on.
Questions about yesno_random
Get a random yes/no answer with an animated GIF. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
yesno_random accepts 1 parameter: force. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for yesno_random: 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 UnClick. Nothing to install.
yesno_random 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 yesno_random 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 yesno_random. 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.
yesno_random is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue