Get logs for one build stage/step.
AI agents call drone_get_build_logs to retrieve information from Drone CI 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 historical log data from a completed or in-progress build stage. It performs a query operation with no side effects, no code execution, no data modification, and no destructive actions. The retrieval of logs is a standard read operation appropriate for monitoring and debugging purposes.
From the tool's definition Tool name 'drone_get_build_logs' and description 'Get logs for one build stage/step' indicate retrieval of build log data with no modification or execution of CI/CD operations.
Attacks that exploit this kind of access
Get logs for one build stage/step. It is categorised as a Read tool in the Drone CI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Drone CI MCP Server MCP server in PolicyLayer and add a rule for drone_get_build_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 Drone CI MCP Server. Nothing to install.
drone_get_build_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 drone_get_build_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 drone_get_build_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.
drone_get_build_logs is provided by the Drone CI MCP Server MCP server (leuzeus/mcp-drone-ci). 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 →