jisho_search
Search Jisho.org Japanese dictionary for words, kanji, or English translations.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/jisho-search.md
What jisho_search does on UnClick
AI agents call jisho_search 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 |
|---|---|---|---|
keyword | string | Yes | Search keyword (English, Japanese, romaji). |
Parameters from the server's own tool schema.
Why jisho_search is rated Low
This tool retrieves information from a dictionary service without side effects. It performs a simple lookup operation that reads data and returns results. No data is created, modified, deleted, or irreversibly changed. No code execution or financial operations are involved. This is a straightforward Read operation with minimal risk profile.
From the tool's definition Tool description states 'Search Jisho.org Japanese dictionary for words, kanji, or English translations.' The verb 'search' indicates read-only querying of a public dictionary resource with no data modification, creation, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs jisho_search 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 jisho_search, this is the rule to start with:
jisho_search 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 jisho_search call is checked against it from then on.
Questions about jisho_search
Search Jisho.org Japanese dictionary for words, kanji, or English translations. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
jisho_search accepts 1 parameter: keyword. Required: keyword. 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 jisho_search: 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.
jisho_search 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 jisho_search 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 jisho_search. 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.
jisho_search 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