Find runbooks in an Octopus Deploy project. Two project kinds are supported: - DB-backed projects: address runbooks by
AI agents call find_runbooks 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 information about runbooks within an Octopus Deploy project. It performs a search query without creating, modifying, deleting, or executing any operations. The server is explicitly positioned as read-only for diagnostic and inspection purposes. No data is altered, no code is executed, and no financial transactions occur. This is a pure information retrieval operation with minimal risk.
From the tool's definition Tool name 'find_runbooks' and description 'Find runbooks in an Octopus Deploy project' indicate a query/search operation.
Documented attack patterns abuse exactly the kind of access find_runbooks 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_runbooks:
{
"version": "1",
"default": "deny",
"tools": {
"find_runbooks": {}
}
}find_runbooks 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 runbooks in an Octopus Deploy project. Two project kinds are supported: - DB-backed projects: address runbooks by. 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_runbooks: 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_runbooks 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_runbooks 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_runbooks. 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_runbooks 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.