Get tiles that haven
AI agents call get_unexplored_tiles to retrieve information from Tiling Trees MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries the state of tiles marked as unexplored within a hierarchical research tree structure. There are no side effects, no data modification, no code execution, and no irreversible actions. It is a pure read operation conforming to the 'Read' category definition of retrieving or querying data without side effects.
From the tool's definition Tool name 'get_unexplored_tiles' and verb 'Get' indicate data retrieval with no modification. The description is incomplete ('Get tiles that haven') but the 'Get' prefix combined with the read-only nature of querying unexplored tiles confirms this is a…
Attacks that exploit this kind of access
Get tiles that haven. It is categorised as a Read tool in the Tiling Trees MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tiling Trees MCP Server MCP server in PolicyLayer and add a rule for get_unexplored_tiles: 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 Tiling Trees MCP Server. Nothing to install.
get_unexplored_tiles 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 get_unexplored_tiles 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 get_unexplored_tiles. 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.
get_unexplored_tiles is provided by the Tiling Trees MCP Server MCP server (k-chrispens/tiling-trees-mcp). 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 →