detect_language
Detect the language of provided text with confidence score. Parameters: text — Text to detect language of.
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/detect-language.md
What detect_language does on X402 Middleware
AI agents call detect_language to retrieve information from X402 Middleware 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 |
Parameters from the server's own tool schema.
Why detect_language is rated Low
This tool analyzes and returns metadata about input text (language detection with confidence scoring). It performs no side effects, does not execute code, does not modify any data, and does not involve financial transactions. It is a pure read operation that classifies/categorizes text properties. The severity is low because even misuse cannot cause harm—the worst outcome is incorrect language detection results.
From the tool's definition Tool name: detect_language. Description states 'Detect the language of provided text with confidence score.' Parameters: text (input only). No modification, deletion, execution, or financial operations occur.
Attacks that exploit this kind of access
The rule that runs detect_language safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_language, this is the rule to start with:
detect_language 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 X402 Middleware, apply this rule, and every detect_language call is checked against it from then on.
Questions about detect_language
Detect the language of provided text with confidence score. Parameters: text — Text to detect language of. It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
detect_language accepts 1 parameter: text. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for detect_language: 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 X402 Middleware. Nothing to install.
detect_language 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 detect_language 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 detect_language. 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.
detect_language is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue