languagetool_check
Check text for grammar, spelling, and style issues using LanguageTool.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/languagetool-check.md
What languagetool_check does on UnClick
AI agents call languagetool_check 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 check. |
language | string | — | Language code (default: auto). E.g. en-US, de-DE, fr. |
Parameters from the server's own tool schema.
Why languagetool_check is rated Low
This tool performs static analysis on provided text to identify grammar, spelling, and style problems. It retrieves information about potential issues without creating, modifying, deleting, or executing any irreversible actions. The analysis is informational only, making it a Read category tool with low severity since misuse poses minimal risk to data or systems.
From the tool's definition Tool description states 'Check text for grammar, spelling, and style issues using LanguageTool.' The verb 'check' indicates read-only analysis with no data modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs languagetool_check 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 languagetool_check, this is the rule to start with:
languagetool_check 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 languagetool_check call is checked against it from then on.
Questions about languagetool_check
Check text for grammar, spelling, and style issues using LanguageTool. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
languagetool_check accepts 2 parameters: text, language. 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 languagetool_check: 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.
languagetool_check 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 languagetool_check 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 languagetool_check. 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.
languagetool_check 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