group_status

Report per-repo index freshness for every repo in a named group. Returns node/edge counts, last-indexed timestamp, last commit, and a best-effort staleness envelope so the agent can decide whether to re-analyze before querying.

Server OpenCodeHub MCP Server theagenticguy/opencodehub
Category Read
Risk class Low
Parameters 00 required

What group_status does on OpenCodeHub MCP Server

AI agents call group_status to retrieve information from OpenCodeHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why group_status needs a policy

This is a read-only query tool that retrieves metadata about repository indexing status and staleness. It performs only information retrieval to help an agent decide whether to re-analyze, with no side effects. Low severity because misuse could only result in stale analysis decisions, not irreversible harm.

From the tool's definition Tool 'group_status' reports/returns index freshness metrics including 'node/edge counts, last-indexed timestamp, last commit, and a best-effort staleness envelope' — all retrieval operations with no modification, deletion, or execution.

Risk signalsBulk/mass operation — affects multiple targets

Questions about group_status

What does the group_status tool do? +

Report per-repo index freshness for every repo in a named group. Returns node/edge counts, last-indexed timestamp, last commit, and a best-effort staleness envelope so the agent can decide whether to re-analyze before querying. It is categorised as a Read tool in the OpenCodeHub MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on group_status? +

Register the OpenCodeHub MCP Server MCP server in PolicyLayer and add a rule for group_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 OpenCodeHub MCP Server. Nothing to install.

What risk level is group_status? +

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

Can I rate-limit group_status? +

Yes. Add a rate_limit block to the group_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.

How do I block group_status completely? +

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

What MCP server provides group_status? +

group_status is provided by the OpenCodeHub MCP Server MCP server (theagenticguy/opencodehub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.