Get available GitHub Actions for a repository
AI agents call get_github_actions to retrieve information from GitHub Action Trigger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches or lists available GitHub Actions without creating, modifying, deleting, or executing any operations. It is a read-only query operation that retrieves metadata about actions configured in a repository. No side effects or state changes occur.
From the tool's definition Tool name 'get_github_actions' and description 'Get available GitHub Actions for a repository' indicate a retrieval/query operation with no modification of data.
Attacks that exploit this kind of access
Get available GitHub Actions for a repository. It is categorised as a Read tool in the GitHub Action Trigger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Action Trigger MCP Server MCP server in PolicyLayer and add a rule for get_github_actions: 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 Action Trigger MCP Server. Nothing to install.
get_github_actions 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_github_actions 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_github_actions. 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_github_actions is provided by the GitHub Action Trigger MCP Server MCP server (nextdriveioe/github-action-trigger-mcp). 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 →