Find tenants in a space - can retrieve a single tenant by ID or list all tenants This unified tool can either: - Get details for a specific tenant when tenantId is provided, including the projects and environments the tenant is associated with - List all tenants in a space when tenantId is omitte...
AI agents call find_tenants to retrieve information from Octopus Deploy MCP Server 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 tenant information without any side effects or state modifications. It falls squarely into the Read category as a data retrieval operation. Severity is low because tenant metadata retrieval poses minimal risk—it does not affect infrastructure, deployments, or financial systems, and misuse would only expose existing configuration data.
From the tool's definition Tool description explicitly states it can 'retrieve a single tenant by ID or list all tenants' and 'Get details for a specific tenant'. The server description emphasizes 'read-only access' to resources.
Documented attack patterns abuse exactly the kind of access find_tenants gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octopus Deploy MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_tenants:
{
"version": "1",
"default": "deny",
"tools": {
"find_tenants": {}
}
}find_tenants 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.
Find tenants in a space - can retrieve a single tenant by ID or list all tenants This unified tool can either: - Get details for a specific tenant when tenantId is provided, including the projects and environments the tenant is associated with - List all tenants in a space when tenantId is omitted ${tenantsDescription} Optionally provide filtering and pagination parameters when listing. It is categorised as a Read tool in the Octopus Deploy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Octopus Deploy MCP Server MCP server in PolicyLayer and add a rule for find_tenants: 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 Octopus Deploy MCP Server. Nothing to install.
find_tenants 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 find_tenants 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 find_tenants. 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.
find_tenants is provided by the Octopus Deploy MCP Server MCP server (octopusdeploy/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 30 Octopus Deploy MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 Octopus Deploy MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.