This record as markdown: /tools/creativelead-unclick/discord-read.md
What discord_read does on UnClick
AI agents call discord_read 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 |
|---|---|---|---|
limit | number | — | |
before | string | — | |
bot_token | string | — | |
channel_id | string | — |
Parameters from the server's own tool schema.
Why discord_read is rated Low
This tool retrieves existing Discord messages without side effects. It is clearly a Read operation. Severity is medium rather than low because unauthorized message reading could expose sensitive communications, PII, or private conversations if an AI agent accesses channels it shouldn't have permission for.
From the tool's definition Tool name explicitly contains 'read' and description states 'Read messages from a Discord channel' - a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs discord_read 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 discord_read, this is the rule to start with:
discord_read 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 discord_read call is checked against it from then on.
Questions about discord_read
Read messages from a Discord channel. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
discord_read accepts 4 parameters: limit, before, bot_token, channel_id. 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 discord_read: 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.
discord_read 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 discord_read 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 discord_read. 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.
discord_read is provided by the UnClick MCP server (creativelead/unclick). 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