bored_by_participants
Get an activity for a specific number of participants.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/bored-by-participants.md
What bored_by_participants does on UnClick
AI agents call bored_by_participants 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 |
|---|---|---|---|
participants | number | Yes | Number of participants |
Parameters from the server's own tool schema.
Why bored_by_participants is rated Low
This tool retrieves activity suggestions based on a participant count parameter. It is a read-only query operation with no capability to modify, delete, execute code, or affect external systems. The blast radius of misuse is minimal—an agent could at worst spam requests or retrieve irrelevant suggestions, neither of which causes harm.
From the tool's definition Tool name 'bored_by_participants' and description 'Get an activity for a specific number of participants' indicate a query/retrieval operation with no side effects. The verb 'Get' explicitly denotes data retrieval.
Attacks that exploit this kind of access
The rule that runs bored_by_participants 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 bored_by_participants, this is the rule to start with:
bored_by_participants 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 bored_by_participants call is checked against it from then on.
Questions about bored_by_participants
Get an activity for a specific number of participants. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
bored_by_participants accepts 1 parameter: participants. Required: participants. 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 bored_by_participants: 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.
bored_by_participants 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 bored_by_participants 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 bored_by_participants. 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.
bored_by_participants 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