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 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
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. Intercept'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.
tools:
location-tool:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Rhombus Node policy for all 30 tools.
Agents calling write-class tools like location-tool have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
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.
Add a rule in your Intercept YAML policy under the tools section for location-tool. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Rhombus Node MCP server.
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 Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept