set_active_source

Set the active pipeline object by its registered name.

SERVERCLIO Adios SOURCEpypi:clio-kit

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/set-active-source.md

WHAT IT DOES

What set_active_source does on CLIO Adios

AI agents use set_active_source to create or update resources in CLIO Adios, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CLIO Adios environment.

RISK

Why set_active_source is rated Medium

This tool modifies the state of the application by changing which pipeline object is active. It's a stateful write operation that alters the active context/selection within the pipeline, but does not delete or irreversibly destroy data. It is reversible by setting a different active source.

From the tool's definition Set the active pipeline object by its registered name

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_active_source safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_active_source, this is the rule to start with:

set_active_source Rate-limited

set_active_source stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_active_source": {
      "limits": [
        {
          "counter": "set_active_source_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CLIO Adios, apply this rule, and every set_active_source call is checked against it from then on.

FAQ

Questions about set_active_source

What does the set_active_source tool do? +

Set the active pipeline object by its registered name. It is categorised as a Write tool in the CLIO Adios MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_active_source? +

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

What risk level is set_active_source? +

set_active_source is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_active_source? +

Yes. Add a rate_limit block to the set_active_source 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 set_active_source completely? +

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

set_active_source is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CLIO Adios, and thousands of servers like it.

This server

All 204 CLIO Adios tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →