the getPrivateLocations tool can retrieve all private locations configured for that org. A private location is a server that can be used to access a test target behind a firewall or VPN.
AI agents call getPrivateLocations to retrieve information from Octomind without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing configuration data (private locations) without modifying, deleting, or executing anything. It has no side effects beyond data retrieval. The sensitivity of the returned data (network infrastructure details) is mitigated by the fact that an authenticated org member would typically have legitimate access to their own infrastructure inventory.
From the tool's definition the getPrivateLocations tool can retrieve all private locations configured for that org
Documented attack patterns abuse exactly the kind of access getPrivateLocations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octomind, and nothing reaches the server without passing your rules. This is the rule we recommend for getPrivateLocations:
{
"version": "1",
"default": "deny",
"tools": {
"getPrivateLocations": {}
}
} getPrivateLocations is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
the getPrivateLocations tool can retrieve all private locations configured for that org. A private location is a server that can be used to access a test target behind a firewall or VPN. It is categorised as a Read tool in the Octomind MCP Server, which means it retrieves data without modifying state.
Register the Octomind MCP server in PolicyLayer and add a rule for getPrivateLocations: 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 Octomind. Nothing to install.
getPrivateLocations 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 getPrivateLocations 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 getPrivateLocations. 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.
getPrivateLocations is provided by the Octomind MCP server (octomind-dev/octomind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octomind, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 Octomind tools catalogued and risk-classified — across an index of 43,000+ MCP servers.