Find the latitude and longitude for a given city name.
Part of the Measure Space server.
Free to start. No card required.
AI agents use convert_city_to_latitude_longitude to create or modify resources in Measure Space. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call convert_city_to_latitude_longitude repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Measure Space.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"convert_city_to_latitude_longitude": {
"limits": [
{
"counter": "convert_city_to_latitude_longitude_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Measure Space policy for all 12 tools.
These attack patterns abuse exactly the kind of access convert_city_to_latitude_longitude gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Find the latitude and longitude for a given city name.. It is categorised as a Write tool in the Measure Space MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Measure Space MCP server in PolicyLayer and add a rule for convert_city_to_latitude_longitude: 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 Measure Space. Nothing to install.
convert_city_to_latitude_longitude is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the convert_city_to_latitude_longitude 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_city_to_latitude_longitude. 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_city_to_latitude_longitude is provided by the Measure Space MCP server (@measurespace/measure-space-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Measure Space tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.