Walk every repo in a named group, run HTTP / gRPC / topic contract extractors, and write
AI agents use group_sync to create or update resources in OpenCodeHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenCodeHub MCP Server environment.
The tool scans repositories, runs extractors, and writes results to the system. This is a Write operation as it modifies the knowledge graph with new/updated contract data. It does not delete data irreversibly, execute arbitrary user-supplied code, or involve financial transactions.
From the tool's definition 'walk every repo in a named group, run HTTP / gRPC / topic contract extractors, and write' — the tool writes extracted contract data back to the knowledge graph
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Walk every repo in a named group, run HTTP / gRPC / topic contract extractors, and write. It is categorised as a Write tool in the OpenCodeHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenCodeHub MCP Server MCP server in PolicyLayer and add a rule for group_sync: 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.
group_sync is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the group_sync 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_sync. 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_sync 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.
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 →