event

Review action to perform. (string, optional)

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/event.md

WHAT IT DOES

What event does on GitHub

AI agents call event 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 event is rated Low

The tool appears to retrieve or query event information from GitHub actions workflows based on its naming and the context of sibling tools (actions_list, actions_get suggest read operations). Without evidence of modification, execution triggering, or deletion, this classifies as Read.

From the tool's definition Tool name 'event' with description 'Review action to perform' appears to be a parameter or retrieval mechanism for examining GitHub actions/events rather than executing or modifying them. The passive 'review' language suggests querying or listing event data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs event 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 event, this is the rule to start with:

event Allowed

event 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": {
    "event": {}
  }
}

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 event call is checked against it from then on.

FAQ

Questions about event

What does the event tool do? +

Review action to perform. (string, optional). 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 event? +

Register the GitHub MCP server in PolicyLayer and add a rule for event: 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 event? +

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

Can I rate-limit event? +

Yes. Add a rate_limit block to the event 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 event completely? +

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

event 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_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

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