List all available languages for spell checking
AI agents call list_languages 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 is a straightforward information retrieval tool that returns metadata about supported languages. It has no write capability, does not execute code or external operations, does not delete data, and involves no financial transactions. The blast radius of misuse is minimal—an agent could only retrieve information about available languages, which is harmless.
From the tool's definition Tool name 'list_languages' and description 'List all available languages for spell checking' indicate a retrieval operation with no side effects. It queries available language options without modifying, executing, or destroying any data.
Attacks that exploit this kind of access
List all available languages for spell checking. 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 list_languages: 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.
list_languages 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 list_languages 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 list_languages. 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.
list_languages 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 →