List all contributor-proposed shadow rules: adopted (in production observation-only mode, with 30-day promotion windows) and queued_for_review (proposed but not yet wired). Each row carries proposer handle, frame, source post URL, rule_id, code_location, shadow_log path, review window, and curren...
Part of the Ibitlabs MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call list_adopted_rules to retrieve information from Ibitlabs 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 list_adopted_rules 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.
tools:
list_adopted_rules:
rules:
- action: allowSee the full Ibitlabs policy for all 5 tools.
Agents calling read-class tools like list_adopted_rules have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
List all contributor-proposed shadow rules: adopted (in production observation-only mode, with 30-day promotion windows) and queued_for_review (proposed but not yet wired). Each row carries proposer handle, frame, source post URL, rule_id, code_location, shadow_log path, review window, and current points. Sourced from /data/contributors.json. Use to see who has contributed encodable frames to the bot.. It is categorised as a Read tool in the Ibitlabs MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for list_adopted_rules. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ibitlabs MCP server.
list_adopted_rules 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 list_adopted_rules rule in your Intercept 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 Intercept policy for list_adopted_rules. 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.
list_adopted_rules is provided by the Ibitlabs MCP server (ibitlabs-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.