Search any file in the data directory for matching entries.
AI agents call search_data_file 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 operation on static game data files, similar to other Read-category tools on this server like 'osrs_wiki_search' and 'search_invtypes'. It retrieves information without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—it only exposes existing game data that is already publicly available through the OSRS Wiki API.
From the tool's definition Tool name 'search_data_file' and description 'Search any file in the data directory for matching entries' indicate querying/retrieval operations with no modification capability.
Attacks that exploit this kind of access
Search any file in the data directory for matching entries. 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 search_data_file: 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.
search_data_file 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 search_data_file 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 search_data_file. 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.
search_data_file 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 →