word_count
Count words, characters, sentences, and estimate reading time.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/word-count.md
What word_count does on UnClick
AI agents call word_count 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 |
|---|---|---|---|
text | string | Yes | Text to analyze. |
Parameters from the server's own tool schema.
Why word_count is rated Low
This tool only retrieves statistics from text input without creating, modifying, deleting, executing, or triggering external operations. It is purely informational analysis with no ability to affect state or external systems.
From the tool's definition Tool performs counting and estimation operations on input text: 'Count words, characters, sentences, and estimate reading time.' These are read-only analytics with no side effects.
Attacks that exploit this kind of access
The rule that runs word_count 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 word_count, this is the rule to start with:
word_count 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 word_count call is checked against it from then on.
Questions about word_count
Count words, characters, sentences, and estimate reading time. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
word_count accepts 1 parameter: text. Required: text. 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 word_count: 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.
word_count 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 word_count 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 word_count. 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.
word_count 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