actions_get

Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts)

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/actions-get.md

WHAT IT DOES

What actions_get does on GitHub

AI agents call actions_get to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why actions_get is rated Low

This tool retrieves metadata and details about existing GitHub Actions workflows, runs, jobs, and artifacts. It performs a read-only query operation with no side effects, does not execute workflows, and does not modify any resources. The 'get' verb and 'details' language confirm informational retrieval only.

From the tool's definition Tool name 'actions_get' and description 'Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts)' indicate a retrieval operation with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs actions_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For actions_get, this is the rule to start with:

actions_get Allowed

actions_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "actions_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every actions_get call is checked against it from then on.

FAQ

Questions about actions_get

What does the actions_get tool do? +

Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts). It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on actions_get? +

Register the GitHub MCP server in PolicyLayer and add a rule for actions_get: 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. Nothing to install.

What risk level is actions_get? +

actions_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit actions_get? +

Yes. Add a rate_limit block to the actions_get 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.

How do I block actions_get completely? +

Set action: deny in the PolicyLayer policy for actions_get. 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.

What MCP server provides actions_get? +

actions_get is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →