ura_planning_decisions
AI agents call ura_planning_decisions to retrieve information from OneMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool almost certainly retrieves or queries planning decision data from Singapore's URA database without modifying it. The tool description is empty, reducing confidence slightly, but the naming convention, server purpose, and sibling tool patterns strongly indicate a read-only query operation with no side effects.
From the tool's definition Tool name 'ura_planning_decisions' suggests retrieval of Urban Redevelopment Authority planning decisions data. The OneMap server description emphasizes 'location searches' and 'accessing thematic layers' and 'population statistics' as read-only operations.
Attacks that exploit this kind of access
ura_planning_decisions. It is categorised as a Read tool in the OneMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OneMap MCP Server MCP server in PolicyLayer and add a rule for ura_planning_decisions: 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 OneMap MCP Server. Nothing to install.
ura_planning_decisions 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 ura_planning_decisions 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 ura_planning_decisions. 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.
ura_planning_decisions is provided by the OneMap MCP Server MCP server (linzele/mcp-onemap). 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 →