Search the OSRS Wiki for pages matching a search term.
AI agents call osrs_wiki_search to retrieve information from OSRS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search query against the OSRS Wiki, returning matching pages. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move resources. It is a straightforward information retrieval operation, consistent with other Read category tools like search, query, and fetch.
From the tool's definition Tool name 'osrs_wiki_search' and description 'Search the OSRS Wiki for pages matching a search term' indicate a read-only operation that retrieves wiki data without modifying or executing anything.
Attacks that exploit this kind of access
Search the OSRS Wiki for pages matching a search term. It is categorised as a Read tool in the OSRS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OSRS MCP Server MCP server in PolicyLayer and add a rule for osrs_wiki_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 OSRS MCP Server. Nothing to install.
osrs_wiki_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 osrs_wiki_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 osrs_wiki_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.
osrs_wiki_search is provided by the OSRS MCP Server MCP server (joshhmann/mcp-osrs). 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 →