Retrieve the detailed deployment logs for a specific deployment.
AI agents call get_deploy_logs to retrieve information from Otoinstall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical deployment logs for inspection and troubleshooting purposes. It is a non-destructive query operation with no side effects—it does not create, modify, execute code, delete data, or commit financial transactions. The blast radius of misuse is minimal, as reading logs cannot directly harm infrastructure or trigger unintended operations.
From the tool's definition Tool name 'get_deploy_logs' and description 'Retrieve the detailed deployment logs for a specific deployment' indicate a read-only operation that queries and returns existing log data without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Retrieve the detailed deployment logs for a specific deployment. It is categorised as a Read tool in the Otoinstall MCP Server, which means it retrieves data without modifying state.
Register the Otoinstall MCP server in PolicyLayer and add a rule for get_deploy_logs: 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 Otoinstall. Nothing to install.
get_deploy_logs 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 get_deploy_logs 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 get_deploy_logs. 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.
get_deploy_logs is provided by the Otoinstall MCP server (otoinstall-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →