coordination_topology
Configure swarm topology Use when native Task is wrong because the work crosses multiple agents that need to vote/sync/load-balance — TodoWrite + a single Task cannot orchestrate consensus. For one-off subtask dispatch, native Task is fine.
This record as markdown: /tools/hamza-agent-hub-252/coordination-topology.md
What coordination_topology does on Hamza Agent Hub 252
AI agents use coordination_topology to create or update resources in Hamza Agent Hub 252, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hamza Agent Hub 252 environment.
Why coordination_topology is rated Medium
This tool modifies the topology and coordination configuration of a multi-agent swarm system. While it does not delete data (Destructive) or move money (Financial), it changes the operational configuration of agent orchestration. The severity is high because misconfiguration could cause agents to malfunction, create loops, or behave unexpectedly across the swarm.
From the tool's definition Tool description states 'Configure swarm topology' and describes modifying how multiple agents coordinate (vote/sync/load-balance). 'Configure' indicates modification of system state.
Attacks that exploit this kind of access
The rule that runs coordination_topology safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For coordination_topology, this is the rule to start with:
coordination_topology stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every coordination_topology call is checked against it from then on.
Questions about coordination_topology
Configure swarm topology Use when native Task is wrong because the work crosses multiple agents that need to vote/sync/load-balance — TodoWrite + a single Task cannot orchestrate consensus. For one-off subtask dispatch, native Task is fine. It is categorised as a Write tool in the Hamza Agent Hub 252 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for coordination_topology: 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 Hamza Agent Hub 252. Nothing to install.
coordination_topology 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 coordination_topology 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 coordination_topology. 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.
coordination_topology is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hamza Agent Hub 252, and thousands of servers like it.
This server
Across the catalogue