get_active_source_names_by_type

List pipeline source names, optionally filtered by type.

SERVERCLIO Adios SOURCEpypi:clio-kit
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-iowarp-adios-mcp/get-active-source-names-by-type.md

What get_active_source_names_by_type does on CLIO Adios

AI agents call get_active_source_names_by_type to retrieve information from CLIO Adios without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_active_source_names_by_type is rated Low

This tool performs a passive enumeration of existing pipeline source names, optionally filtered by type. It retrieves metadata about available sources without creating, modifying, deleting, or executing any external operations. The blast radius of misuse is minimal—an agent could only discover what sources exist, with no capability to alter system state or trigger actions.

From the tool's definition Tool description states it 'List pipeline source names' — a retrieval operation with no modification or side effects. The verb 'List' and the noun phrase 'source names' indicate a read-only data query operation.

Questions about get_active_source_names_by_type

What does the get_active_source_names_by_type tool do? +

List pipeline source names, optionally filtered by type. It is categorised as a Read tool in the CLIO Adios MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_active_source_names_by_type? +

Register the CLIO Adios MCP server in PolicyLayer and add a rule for get_active_source_names_by_type: 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 get_active_source_names_by_type? +

get_active_source_names_by_type is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_active_source_names_by_type? +

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

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

get_active_source_names_by_type 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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CLIO Adios's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.