ura_residential_pipeline
AI agents call ura_residential_pipeline 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.
Despite empty description, the tool name and server context indicate this retrieves or queries publicly available residential pipeline information without modifying or deleting data. The 'get_*' and thematic data retrieval pattern on this OneMap server strongly suggests a read-only data access tool.
From the tool's definition Tool name 'ura_residential_pipeline' suggests querying residential development pipeline data from Singapore's Urban Redevelopment Authority.
Attacks that exploit this kind of access
ura_residential_pipeline. 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_residential_pipeline: 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_residential_pipeline 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_residential_pipeline 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_residential_pipeline. 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_residential_pipeline 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 →