Search the buyer org's structured conflict-party log across every scope. Use for an OCG / Rule 1.7 prior-representation check before dispatching new work. Filter by party name (case-insensitive substring), optional party_type, and optional lookback window. Returns the scopes where the party appea...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Scope (AEC) - Preview server.
Free to start. No card required.
AI agents call scope_conflict_log 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_conflict_log 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.
{
"version": "1",
"default": "deny",
"tools": {
"scope_conflict_log": {}
}
}See the full Scope (AEC) - Preview policy for all 30 tools.
These attack patterns abuse exactly the kind of access scope_conflict_log gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search the buyer org's structured conflict-party log across every scope. Use for an OCG / Rule 1.7 prior-representation check before dispatching new work. Filter by party name (case-insensitive substring), optional party_type, and optional lookback window. Returns the scopes where the party appears, the matched entries on each scope, and a total count.. It is categorised as a Read tool in the Scope (AEC) - Preview MCP Server, which means it retrieves data without modifying state.
Register the Scope (AEC) - Preview MCP server in PolicyLayer and add a rule for scope_conflict_log: 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_conflict_log 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 scope_conflict_log 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_conflict_log. 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_conflict_log 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.