get_household_size
AI agents call get_household_size 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 retrieves statistics about household sizes—a read-only operation with no side effects. No data is created, modified, or deleted. The lack of description slightly lowers confidence, but the function name and server context strongly indicate a simple data lookup. Even if misused by an AI agent, the impact is limited to unauthorized data access rather than modification or destruction of information.
From the tool's definition Tool name 'get_household_size' indicates a data retrieval operation. The tool description is empty, but the naming pattern matches sibling tools like 'get_all_planning_areas' and 'get_all_themes_info' which are clearly read operations.
Attacks that exploit this kind of access
get_household_size. 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_household_size: 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_household_size 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_household_size 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_household_size. 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_household_size 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 →