published

Filter by publish date or date range (ISO 8601 date or range). (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/published.md

WHAT IT DOES

What published does on GitHub

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

This is a filtering/search parameter used to narrow query results based on temporal criteria. It has no side effects, creates no data, executes no code, and deletes nothing. It is purely a read operation that helps retrieve information. The low severity reflects that misuse would only affect data visibility, not integrity or availability.

From the tool's definition Tool filters by publish date using ISO 8601 date formats. The description 'Filter by publish date or date range' indicates a query/search parameter that retrieves or queries data without modifying anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

published Allowed

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

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

FAQ

Questions about published

What does the published tool do? +

Filter by publish date or date range (ISO 8601 date or range). (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 published? +

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

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

Can I rate-limit published? +

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

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

published 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

The MCP Attack Database →

Guides

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