braille_convert
Convert text to Braille Unicode dots or decode Braille back to text.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/braille-convert.md
What braille_convert does on UnClick
AI agents call braille_convert 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 or Braille characters to convert. |
Parameters from the server's own tool schema.
Why braille_convert is rated Low
This tool performs a pure text transformation/conversion with no side effects — it neither stores data, executes commands, nor modifies external systems. It simply encodes or decodes text to/from Braille Unicode, making it a read/transform operation with minimal risk.
From the tool's definition Convert text to Braille Unicode dots or decode Braille back to text
Attacks that exploit this kind of access
The rule that runs braille_convert 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 braille_convert, this is the rule to start with:
braille_convert 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 braille_convert call is checked against it from then on.
Questions about braille_convert
Convert text to Braille Unicode dots or decode Braille back to text. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
braille_convert accepts 1 parameter: text. 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 braille_convert: 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.
braille_convert 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 braille_convert 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 braille_convert. 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.
braille_convert 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