get_workflow

Retrieve a registered MCP prompt by name and return its workflow instructions as text.

SERVERIconnect SOURCEiconnect-mcp

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-heznpc-iconnect/get-workflow.md

WHAT IT DOES

What get_workflow does on Iconnect

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

RISK

Why get_workflow is rated Low

This tool retrieves and returns data (workflow instructions) without modifying, deleting, or executing any operations. It is a straightforward read operation that queries stored prompt/workflow information and returns it to the caller.

From the tool's definition Tool description states 'Retrieve a registered MCP prompt by name and return its workflow instructions as text.' The verb 'Retrieve' and the read-only nature of returning existing workflow instructions indicate no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_workflow safely

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

get_workflow Allowed

get_workflow is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workflow": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_workflow

What does the get_workflow tool do? +

Retrieve a registered MCP prompt by name and return its workflow instructions as text. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workflow? +

Register the Iconnect MCP server in PolicyLayer and add a rule for get_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 Iconnect. Nothing to install.

What risk level is get_workflow? +

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

Can I rate-limit get_workflow? +

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

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

get_workflow is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →