text_readability
Analyze text readability with Flesch-Kincaid grade and reading ease scores.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/text-readability.md
What text_readability does on UnClick
AI agents call text_readability 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 for readability. |
Parameters from the server's own tool schema.
Why text_readability is rated Low
This tool performs a static analysis of text input to compute readability metrics (Flesch-Kincaid grade and reading ease scores). It retrieves and calculates metrics from provided text without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is minimal—an agent could only waste compute resources or analyze unwanted text, with no destructive or financial consequences.
From the tool's definition Tool description states 'Analyze text readability' with scoring metrics. The verb 'analyze' indicates data retrieval and assessment with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs text_readability 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 text_readability, this is the rule to start with:
text_readability 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 text_readability call is checked against it from then on.
Questions about text_readability
Analyze text readability with Flesch-Kincaid grade and reading ease scores. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
text_readability 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 text_readability: 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.
text_readability 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 text_readability 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 text_readability. 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.
text_readability 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