Search the Octopus Deploy audit log (also called the Events log) — every meaningful action recorded against a space: deployments, release creations, modifications, user logins, machine registrations, variable edits, tenant changes, and so on. Modes (the \
AI agents call find_events 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.
find_events queries audit log data to retrieve and inspect past actions and events. It has no side effects, creates no new resources, executes no code, and does not delete or modify data. This is a pure data retrieval operation, fitting the Read category. Severity is low because audit log searches pose minimal risk—they expose operational history but cannot modify infrastructure or trigger deployments.
From the tool's definition Tool description explicitly states 'Search the Octopus Deploy audit log' and 'read-only access' is emphasized in the server description. The tool retrieves historical event records without modifying, deleting, or executing operations.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access find_events 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_events:
{
"version": "1",
"default": "deny",
"tools": {
"find_events": {}
}
}find_events 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.
Search the Octopus Deploy audit log (also called the Events log) — every meaningful action recorded against a space: deployments, release creations, modifications, user logins, machine registrations, variable edits, tenant changes, and so on. Modes (the \. 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_events: 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_events 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_events 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_events. 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_events 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.