AI agents call random_card 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 |
|---|---|---|---|
count | integer | — | Number of cards to draw |
include_jokers | boolean | — | Include joker cards |
Parameters from the server's own tool schema.
This tool generates random card selections from a standard deck, which is a read operation that retrieves data without modifying any persistent state. There are no destructive, financial, or code execution implications. The severity is low because misuse would only produce random card outputs with no harmful consequences.
From the tool's definition Tool 'random_card' draws random playing card(s) from a deck. The verb 'draw' in the context of card operations and the server description indicating 'deterministic tools' for mathematical and utility operations indicates this retrieves/queries data from a…
Attacks that exploit this kind of access
Draw random playing card(s) from a deck. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
random_card accepts 2 parameters: count, include_jokers. 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 random_card: 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.
random_card 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 random_card 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 random_card. 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.
random_card 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.
random_card 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 →