High Risk →

screen

Run a flexible OpenInsider screener query with custom filters (transaction type, role, value range, date range, etc.).

High parameter count (15 properties)

Part of the Openinsider MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

openinsider-mcp Execute

AI agents invoke screen to trigger processes or run actions in Openinsider. 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.

screen can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept 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.

openinsider.yaml
tools:
  screen:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Openinsider policy for all 16 tools.

Tool Name screen
Category Execute
Risk Level High

View all 16 tools →

Agents calling execute-class tools like screen have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

screen is one of the high-risk operations in Openinsider. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the screen tool do? +

Run a flexible OpenInsider screener query with custom filters (transaction type, role, value range, date range, etc.).. It is categorised as a Execute tool in the Openinsider MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on screen? +

Add a rule in your Intercept YAML policy under the tools section for screen. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Openinsider MCP server.

What risk level is screen? +

screen is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit screen? +

Yes. Add a rate_limit block to the screen 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.

How do I block screen completely? +

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

screen is provided by the Openinsider MCP server (openinsider-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.