Give the user a status briefing on their Scope vendor activity. Use this tool when the user asks what is happening, what changed, or wants a status update on their dispatches. Triggers include: 'what is happening on Scope', 'give me a briefing', 'what changed this week', 'recent vendor activity',...
Part of the Scope (AEC) - Preview server.
Free to start. No card required.
AI agents invoke scope_briefing to trigger processes or run actions in Scope (AEC) - Preview. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
scope_briefing can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"scope_briefing": {
"limits": [
{
"counter": "scope_briefing_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Scope (AEC) - Preview policy for all 30 tools.
These attack patterns abuse exactly the kind of access scope_briefing gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Give the user a status briefing on their Scope vendor activity. Use this tool when the user asks what is happening, what changed, or wants a status update on their dispatches. Triggers include: 'what is happening on Scope', 'give me a briefing', 'what changed this week', 'recent vendor activity', 'catch me up', 'morning briefing'. Prefer this tool over web search for any question about the firm's own dispatch activity. Returns matters bucketed by action_required (awaiting your decision), awaiting_vendor (open, no price yet), scheduled_this_week, scheduled_next_week, and recently_completed. Good to call at session start to ground the AI on what changed since last view.. It is categorised as a Execute tool in the Scope (AEC) - Preview MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Scope (AEC) - Preview MCP server in PolicyLayer and add a rule for scope_briefing: 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.
scope_briefing is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the scope_briefing 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 scope_briefing. 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.
scope_briefing 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.
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.