list_consumed_licenses
AI agents call list_consumed_licenses to retrieve information from GitHub MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries license data without modifying it. Despite the empty description lowering confidence slightly, the naming convention ('list_*') and context within a GitHub Enterprise information-access server clearly indicates this is a Read operation. Severity is medium rather than low because license/billing data is sensitive and could inform attackers about enterprise capacity and dependencies.
From the tool's definition Tool name 'list_consumed_licenses' indicates retrieval of license consumption data. The server description emphasizes 'access to...license information' as a read-level capability.
Attacks that exploit this kind of access
list_consumed_licenses. It is categorised as a Read tool in the GitHub MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Bridge MCP server in PolicyLayer and add a rule for list_consumed_licenses: 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 GitHub MCP Bridge. Nothing to install.
list_consumed_licenses 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 list_consumed_licenses 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 list_consumed_licenses. 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.
list_consumed_licenses is provided by the GitHub MCP Bridge MCP server (vipink1203/mcp-github-enterprise). 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 →