Get all root-level groups (groups with no parent)
AI agents call get_root_groups to retrieve information from Sidvy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves organizational metadata about group hierarchy without modifying, executing operations, or deleting data. It is a straightforward query operation that returns information about existing workspace structure. The blast radius of misuse is minimal—an attacker could only learn about the group organization structure, which is read-only information.
From the tool's definition The tool name 'get_root_groups' and description 'Get all root-level groups (groups with no parent)' indicate a retrieval operation with no side effects. The verb 'Get' and the query nature (listing root-level groups) are characteristic of Read operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get all root-level groups (groups with no parent). It is categorised as a Read tool in the Sidvy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for get_root_groups: 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 Sidvy MCP Server. Nothing to install.
get_root_groups 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 get_root_groups 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 get_root_groups. 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.
get_root_groups is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-mcp). 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 →