updated
Filter by update date or date range (ISO 8601 date or range). (string, optional)
This record as markdown: /tools/io-github-aifity-omnigit-mcp/updated.md
What updated does on GitHub
AI agents call updated 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.
Why updated is rated Low
This appears to be a filter parameter used to narrow query results by update date, not a tool that performs any action on its own. It is a read-only filtering mechanism. Confidence is low because the description is minimal and it's unclear how this parameter is used in context, but filtering/querying implies Read with low severity.
From the tool's definition 'Filter by update date or date range (ISO 8601 date or range)' — this is a filter/query parameter, not a standalone action
Attacks that exploit this kind of access
The rule that runs updated 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 updated, this is the rule to start with:
updated is read-only, so it stays allowed. 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 updated call is checked against it from then on.
Questions about updated
Filter by update 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.
Register the GitHub MCP server in PolicyLayer and add a rule for updated: 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.
updated is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the updated 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 updated. 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.
updated 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