Find terrain-valid locations for placing a POI/structure. Returns ranked candidates by suitability.
AI agents call find_valid_poi_location to retrieve information from Rpg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search/query operation across the game world's terrain data to identify suitable locations. It has no side effects, does not execute code or external operations, and does not modify game state. The blast radius of misuse is minimal—an AI agent could only receive incorrect location suggestions, which would not break game mechanics or cause irreversible harm.
From the tool's definition The tool 'find_valid_poi_location' returns ranked candidates for locations without modifying any data. The verb 'find' and 'returns' indicate a query/retrieval operation.
Documented attack patterns abuse exactly the kind of access find_valid_poi_location gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rpg, and nothing reaches the server without passing your rules. This is the rule we recommend for find_valid_poi_location:
{
"version": "1",
"default": "deny",
"tools": {
"find_valid_poi_location": {}
}
} find_valid_poi_location is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find terrain-valid locations for placing a POI/structure. Returns ranked candidates by suitability. It is categorised as a Read tool in the Rpg MCP Server, which means it retrieves data without modifying state.
Register the Rpg MCP server in PolicyLayer and add a rule for find_valid_poi_location: 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 Rpg. Nothing to install.
find_valid_poi_location 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 find_valid_poi_location 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 find_valid_poi_location. 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.
find_valid_poi_location is provided by the Rpg MCP server (mnehmos/mnehmos.rpg.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rpg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
47 Rpg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.