Check index freshness and sync staleness for all repos in a group. Flags repos that have not been indexed or are stale (>24h).
AI agents call group_status to retrieve information from code-intel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports metadata about repository indexing status without modifying any underlying data or triggering side effects. It is a diagnostic/monitoring function that queries existing state, placing it clearly in the Read category with low severity since misuse cannot cause data loss, code execution, or irreversible changes.
From the tool's definition Tool description states it 'checks index freshness and sync staleness' and 'flags repos' — purely informational operations with no data modification, deletion, or code execution. The verb 'check' and 'flags' indicate read-only status reporting.
Attacks that exploit this kind of access
Check index freshness and sync staleness for all repos in a group. Flags repos that have not been indexed or are stale (>24h). It is categorised as a Read tool in the code-intel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the code-intel 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 code-intel MCP Server. Nothing to install.
group_status 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 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.
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.
group_status is provided by the code-intel MCP Server MCP server (vohongtho/code-intel-platform). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →