Low Risk

get_supported_languages

Get list of supported OCR languages.

How to control get_supported_languages ↓

AI agents call get_supported_languages to retrieve information from MCP OCR Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a simple read operation—it queries and returns a static list of supported languages. There are no side effects, no data modification, no code execution, and no capability to trigger external operations. The blast radius of misuse is minimal, as an AI agent cannot cause harm by retrieving this informational list.

From the tool's definition Tool name 'get_supported_languages' and description 'Get list of supported OCR languages' indicate a query operation that retrieves metadata about available languages without modifying any data or triggering external operations.

Documented attack patterns abuse exactly the kind of access get_supported_languages gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP OCR Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_supported_languages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_supported_languages": {}
  }
}

get_supported_languages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP OCR Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_supported_languages tool do? +

Get list of supported OCR languages. It is categorised as a Read tool in the MCP OCR Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_supported_languages? +

Register the MCP OCR Server MCP server in PolicyLayer and add a rule for get_supported_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 MCP OCR Server. Nothing to install.

What risk level is get_supported_languages? +

get_supported_languages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_supported_languages? +

Yes. Add a rate_limit block to the get_supported_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.

How do I block get_supported_languages completely? +

Set action: deny in the PolicyLayer policy for get_supported_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.

What MCP server provides get_supported_languages? +

get_supported_languages is provided by the MCP OCR Server MCP server (rjn32s/mcp-ocr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP OCR Server tool call.

Deterministic rules across all 5 MCP OCR Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

5 MCP OCR Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.