run_osint_workflow · MCP OSINT Server MCP: Risk & Policy

WHAT IT DOES

What run_osint_workflow does on MCP OSINT Server

AI agents invoke run_osint_workflow to trigger actions in MCP OSINT Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_osint_workflow needs a policy

This tool permits execution of external operations (OSINT workflows) whose effects depend on arguments supplied at runtime—the target and optional parameters shape what reconnaissance activities occur.

From the tool's definition The tool name 'run_osint_workflow' and description 'Run any OSINT workflow by name with a target and optional parameters' indicate it executes arbitrary workflows specified by name with user-supplied targets and parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_osint_workflow Rate-limited

run_osint_workflow stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_osint_workflow": {
      "limits": [
        {
          "counter": "run_osint_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP OSINT Server, so you can run agents against it safely.

FAQ

Questions about run_osint_workflow

What does the run_osint_workflow tool do? +

Run any OSINT workflow by name with a target and optional parameters. It is categorised as a Execute tool in the MCP OSINT Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_osint_workflow? +

Register the MCP OSINT Server MCP server in PolicyLayer and add a rule for run_osint_workflow: 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 MCP OSINT Server. Nothing to install.

What risk level is run_osint_workflow? +

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

Can I rate-limit run_osint_workflow? +

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

How do I block run_osint_workflow completely? +

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

run_osint_workflow is provided by the MCP OSINT Server MCP server (lliwi/osint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.