target_date

The target date of the status update in YYYY-MM-DD format. Used for 'create_project_status_update' method. (string, optional)

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

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/target-date.md

WHAT IT DOES

What target_date does on GitHub

AI agents call target_date as a supporting operation in GitHub workflows.

RISK

Why target_date is rated Low

This appears to be a parameter descriptor rather than a standalone tool. It describes a date field used by another method ('create_project_status_update'). On its own it performs no action; it is metadata about an argument. Classified as Other with low confidence due to the uninformative, parameter-like description.

From the tool's definition 'The target date of the status update in YYYY-MM-DD format. Used for create_project_status_update method.'

Attacks that exploit this kind of access

RECOMMENDED RULE

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

target_date Rate-limited

target_date gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "target_date": {
      "limits": [
        {
          "counter": "target_date_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about target_date

What does the target_date tool do? +

The target date of the status update in YYYY-MM-DD format. Used for 'create_project_status_update' method. (string, optional). It is categorised as a Other tool in the GitHub MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on target_date? +

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

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

Can I rate-limit target_date? +

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

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

target_date 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 →Tool risk categories →MCP tool →