List repositories visible to the Drone token.
AI agents call drone_list_repos 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 information about repositories accessible to the authenticated token. It performs a read-only query with no side effects, no code execution, no deletions, and no financial impact. The blast radius of misuse is limited to potential information disclosure about repository names and metadata visible to that token's permissions.
From the tool's definition Tool name 'drone_list_repos' and description 'List repositories visible to the Drone token' indicate a query operation that retrieves repository metadata without modifying or executing anything.
Attacks that exploit this kind of access
List repositories visible to the Drone token. 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_list_repos: 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_list_repos 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_list_repos 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_list_repos. 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_list_repos 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 →