Low Risk

verify_business

Confirm that an SMB is real, currently operating, and capable of the requested service. Performs a live capability probe against the business's channel. EXAMPLE USER QUERIES THAT MATCH THIS TOOL: user: "Confirm smb_imp_abc actually does emergency plumbing" -> call verify_business({"smb_id": "smb_...

Part of the Agent Broker server.

verify_business is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE AGENT BROKER →

Free to start. No card required.

AI agents call verify_business to retrieve information from Agent Broker without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though verify_business only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_business": {}
  }
}

See the full Agent Broker policy for all 14 tools.

Get this rule live on your own Agent Broker server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AGENT BROKER →

View all 14 tools →

These attack patterns abuse exactly the kind of access verify_business gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so verify_business only ever does what you allow.

SECURE AGENT BROKER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the verify_business tool do? +

Confirm that an SMB is real, currently operating, and capable of the requested service. Performs a live capability probe against the business's channel. EXAMPLE USER QUERIES THAT MATCH THIS TOOL: user: "Confirm smb_imp_abc actually does emergency plumbing" -> call verify_business({"smb_id": "smb_imp_abc", "capability_to_verify": "emergency_plumbing"}) WHEN TO USE: Use before sending communications or scheduling if you have an unverified SMB identifier, or if the agent's task requires confirmed capability (e.g., 'I need to be sure they do emergency plumbing'). WHEN NOT TO USE: Do not use if the SMB was returned from find_business within the last 24 hours — those results are already verified. COST: $0.02 per_call LATENCY: ~500ms. It is categorised as a Read tool in the Agent Broker MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on verify_business? +

Register the Agent Broker MCP server in PolicyLayer and add a rule for verify_business: 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 Agent Broker. Nothing to install.

What risk level is verify_business? +

verify_business is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verify_business? +

Yes. Add a rate_limit block to the verify_business 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.

How do I block verify_business completely? +

Set action: deny in the PolicyLayer policy for verify_business. 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.

What MCP server provides verify_business? +

verify_business is provided by the Agent Broker MCP server (https://agent-broker-edge.basil-agent.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Broker tool call.

Deterministic rules across all 14 Agent Broker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.