convert_3414_to_4326
AI agents call convert_3414_to_4326 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.
Coordinate conversion is a pure read/compute operation with no side effects. The tool transforms coordinates between reference systems and returns the result. Empty description lowers confidence slightly, but the naming pattern and server context make the purpose clear.
From the tool's definition Tool name 'convert_3414_to_4326' suggests coordinate system conversion (SVY21/EPSG:3414 to WGS84/EPSG:4326); description is empty but sibling tools like convert_3857_to_4326 and convert_4326_to_3414 confirm this is a coordinate conversion server
Attacks that exploit this kind of access
convert_3414_to_4326. 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 convert_3414_to_4326: 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.
convert_3414_to_4326 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 convert_3414_to_4326 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 convert_3414_to_4326. 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.
convert_3414_to_4326 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 →