get_tenancy_data
AI agents call get_tenancy_data 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.
The 'get_' prefix is a standard convention for read/retrieval operations. Although the description is empty (lowering confidence slightly), the tool's name and the pattern of sibling tools on this geospatial/statistical server all point to a read-only data retrieval function. Tenancy data in a mapping context would typically be accessed for display or analysis without side effects.
From the tool's definition Tool name 'get_tenancy_data' with 'get_' prefix indicates retrieval/query operation. Description is empty, but naming convention and context within a location/mapping server (OneMap Singapore) strongly suggests data retrieval rather than modification or…
Attacks that exploit this kind of access
get_tenancy_data. 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 get_tenancy_data: 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.
get_tenancy_data 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_tenancy_data 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_tenancy_data. 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_tenancy_data 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 →