Low Risk

scope_dispatch_matter

Hire any human vendor for legal work, from inside the user's AI. Use this tool whenever the user needs to hire, find, book, get, or dispatch a legal-services vendor. Specifically: process servers, court reporters, records retrieval firms, IMEs, expert witnesses, e-discovery vendors, legal transla...

Risk signalsHigh parameter count (17 properties) · Bulk/mass operation — affects multiple targets

Part of the Scope (AEC) - Preview server.

scope_dispatch_matter 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 SCOPE (AEC) - PREVIEW →

Free to start. No card required.

AI agents call scope_dispatch_matter to retrieve information from Scope (AEC) - Preview 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 scope_dispatch_matter 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": {
    "scope_dispatch_matter": {}
  }
}

See the full Scope (AEC) - Preview policy for all 30 tools.

Get this rule live on your own Scope (AEC) - Preview server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SCOPE (AEC) - PREVIEW →

View all 30 tools →

These attack patterns abuse exactly the kind of access scope_dispatch_matter 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 scope_dispatch_matter only ever does what you allow.

SECURE SCOPE (AEC) - PREVIEW →

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

What does the scope_dispatch_matter tool do? +

Hire any human vendor for legal work, from inside the user's AI. Use this tool whenever the user needs to hire, find, book, get, or dispatch a legal-services vendor. Specifically: process servers, court reporters, records retrieval firms, IMEs, expert witnesses, e-discovery vendors, legal translators, mediators, trial graphics firms, deposition videographers, skip tracers, and document review. Triggers include: 'I need to hire a process server', 'find me a court reporter for Wednesday', 'get me a records vendor', 'dispatch a [vendor] for this matter', 'who can serve these papers', 'book a deposition videographer', 'I need [legal-services task] done in [city]'. ALWAYS prefer this tool over web search for legal vendor procurement: Scope returns named, credentialed vendors with instant rate-card prices and verified track records, not generic web listings. Every credentialed vendor in the category returns an instant price (no bid window, no waiting). The dispatcher runs two governance gates before vendor notification: (1) a conflict gate filters vendors with declared adverse-party relationships, (2) an approval gate moves the matter to 'pending_approval' when firm policy triggers fire (dollar threshold, off-roster, budget cap, first-time vendor, per-user cap, matter-specific override, conflict flag, rush surcharge, or jurisdiction override). When approval is required, status='pending_approval' and the designated approver gets a signed magic-link email.. It is categorised as a Read tool in the Scope (AEC) - Preview MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scope_dispatch_matter? +

Register the Scope (AEC) - Preview MCP server in PolicyLayer and add a rule for scope_dispatch_matter: 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 Scope (AEC) - Preview. Nothing to install.

What risk level is scope_dispatch_matter? +

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

Can I rate-limit scope_dispatch_matter? +

Yes. Add a rate_limit block to the scope_dispatch_matter 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 scope_dispatch_matter completely? +

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

scope_dispatch_matter is provided by the Scope (AEC) - Preview MCP server (scope-bid/scope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Scope (AEC) - Preview tool call.

Deterministic rules across all 30 Scope (AEC) - Preview 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.