ura_developer_sales
AI agents call ura_developer_sales 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.
Based on the OneMap server's context (location searches, statistics, data access) and the tool name referencing a data category rather than an action verb, this appears to be a read-only data query tool. The empty description lowers confidence slightly, but the functional naming convention strongly suggests passive data retrieval with no side effects.
From the tool's definition Tool name 'ura_developer_sales' suggests querying URA (Urban Redevelopment Authority) developer sales data.
Attacks that exploit this kind of access
ura_developer_sales. 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_developer_sales: 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_developer_sales 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_developer_sales 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_developer_sales. 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_developer_sales 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 →