Check spelling in the provided text and return misspellings with suggestions
AI agents call check_spelling to retrieve information from SpellChecker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs text analysis and spell-checking, returning suggestions without creating, modifying, deleting, executing code, or committing any financial transactions. It retrieves spelling information from provided input and returns results, fitting the Read category. The severity is low because misuse cannot cause harm—an AI agent receiving spelling suggestions has no destructive or unintended consequences.
From the tool's definition Tool name 'check_spelling' and description 'Check spelling in the provided text and return misspellings with suggestions' indicate a read-only operation that analyzes text and returns results without modifying any data.
Attacks that exploit this kind of access
Check spelling in the provided text and return misspellings with suggestions. It is categorised as a Read tool in the SpellChecker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SpellChecker MCP Server MCP server in PolicyLayer and add a rule for check_spelling: 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 SpellChecker MCP Server. Nothing to install.
check_spelling 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 check_spelling 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 check_spelling. 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.
check_spelling is provided by the SpellChecker MCP Server MCP server (morahan/spellchecker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →