Remove a vendor from the buyer's roster entirely. Use when the relationship has changed and you want to revert the vendor to neutral marketplace status (no priority routing, no exclusion). Requires authentication.
Part of the Scope (AEC) - Preview server.
Free to start. No card required.
AI agents may call scope_remove_from_roster to permanently remove or destroy resources in Scope (AEC) - Preview. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call scope_remove_from_roster in a loop, permanently destroying resources in Scope (AEC) - Preview. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"scope_remove_from_roster"
]
}See the full Scope (AEC) - Preview policy for all 30 tools.
These attack patterns abuse exactly the kind of access scope_remove_from_roster gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Remove a vendor from the buyer's roster entirely. Use when the relationship has changed and you want to revert the vendor to neutral marketplace status (no priority routing, no exclusion). Requires authentication.. It is categorised as a Destructive tool in the Scope (AEC) - Preview MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Scope (AEC) - Preview MCP server in PolicyLayer and add a rule for scope_remove_from_roster: 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_remove_from_roster is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the scope_remove_from_roster 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_remove_from_roster. 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_remove_from_roster 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.