This tool performs operations on locations. - 'get': Retrieves all locations. When generating reports with location details, use location names not uuids. - 'create': Creates a new location with a name and optional address. - 'update': Updates an existing location (requires locationUuid). - 'get-...
Part of the Rhombus Node server.
Free to start. No card required.
AI agents use location-tool to create or modify resources in Rhombus Node. 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 location-tool 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 Rhombus Node.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"location-tool": {
"limits": [
{
"counter": "location-tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Rhombus Node policy for all 31 tools.
These attack patterns abuse exactly the kind of access location-tool 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.
This tool performs operations on locations. - 'get': Retrieves all locations. When generating reports with location details, use location names not uuids. - 'create': Creates a new location with a name and optional address. - 'update': Updates an existing location (requires locationUuid). - 'get-labels': Retrieves all location labels for the organization.. It is categorised as a Write tool in the Rhombus Node MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rhombus Node MCP server in PolicyLayer and add a rule for location-tool: 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 Rhombus Node. Nothing to install.
location-tool 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 location-tool 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 location-tool. 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.
location-tool is provided by the Rhombus Node MCP server (rhombus-node-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Rhombus Node 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.