status
The status of the project. Used for 'create_project_status_update' method. (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/status.md
What status does on GitHub
AI agents call status as a supporting operation in GitHub workflows.
Why status is rated Low
This appears to be a parameter descriptor rather than a standalone tool. The description indicates it is an optional string field used as input to another method ('create_project_status_update'). It does not describe an independent action with side effects. Confidence is low because the description is uninformative as a tool definition.
From the tool's definition 'The status of the project. Used for \'create_project_status_update\' method. (string, optional)'
Attacks that exploit this kind of access
The rule that runs status 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 status, this is the rule to start with:
status gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every status call is checked against it from then on.
Questions about status
The status of the project. 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.
Register the GitHub MCP server in PolicyLayer and add a rule for status: 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.
status is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the status 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 status. 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.
status 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue