business_pod_route_backend
ADR-164 Phase 3 — Compute the domain-affinity routing decision for a business pod per ADR-164 §3.4 and return {backend, reason}. The three backends are local-stdio (preferLocalExecution=true), cloud-managed (preferLocalExecution=false AND budgetUsdMonthly >= 50), and remote-peer (everything else ...
This record as markdown: /tools/hamza-agent-hub-252/business-pod-route-backend.md
What business_pod_route_backend does on Hamza Agent Hub 252
AI agents call business_pod_route_backend to retrieve information from Hamza Agent Hub 252 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why business_pod_route_backend is rated Low
The tool computes and returns a routing decision (backend selection and reason) based on input parameters. It does not execute the routing, modify data, or trigger external operations — it purely evaluates logic and returns a recommendation. The description emphasizes auditability and that this is called BEFORE the cost-optimal KRR step, confirming it is a read/query operation with no side effects.
From the tool's definition Compute the domain-affinity routing decision... and return {backend, reason}... surfacing this as an MCP tool keeps the rule auditable from the pod template alone
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs business_pod_route_backend 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 business_pod_route_backend, this is the rule to start with:
business_pod_route_backend is read-only, so it stays allowed. 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 business_pod_route_backend call is checked against it from then on.
Questions about business_pod_route_backend
ADR-164 Phase 3 — Compute the domain-affinity routing decision for a business pod per ADR-164 §3.4 and return {backend, reason}. The three backends are local-stdio (preferLocalExecution=true), cloud-managed (preferLocalExecution=false AND budgetUsdMonthly >= 50), and remote-peer (everything else — small-budget non-local pods route through a federation peer node). Use when a /loop driver, @metaharness/router policy hook, or operator CLI needs the structural routing pick BEFORE the cost-optimal KRR step — surfacing this as an MCP tool keeps the rule auditable from the pod template alone and lets non-TS callers reach it. Re-implementing the rule in the caller is wrong because it forks the §3.4 source-of-truth and skips the {success,valid,error,path} envelope shape callers already rely on from business_pod_validate. Pair with business_pod_validate when pre-flighting a template, since this tool also runs full schema validation and degrades to the same error shape on malformed input. Threshold lives in CLOUD_BUDGET_THRESHOLD_USD in domain-affinity-policy.ts — keep that constant and this description aligned. It is categorised as a Read tool in the Hamza Agent Hub 252 MCP Server, which means it retrieves data without modifying state.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for business_pod_route_backend: 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.
business_pod_route_backend 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 business_pod_route_backend 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 business_pod_route_backend. 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.
business_pod_route_backend 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