get_workflow_tags
Get the tags/categories associated with a workflow.
This record as markdown: /tools/flowdot-llc-mcp-server/get-workflow-tags.md
What get_workflow_tags does on FlowDot MCP Server
AI agents call get_workflow_tags to retrieve information from FlowDot MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_workflow_tags is rated Low
This tool queries and returns metadata (tags/categories) about an existing workflow. It performs no creation, modification, deletion, or execution of external operations. The operation is purely informational and has no impact on system state or data integrity.
From the tool's definition Tool name 'get_workflow_tags' and description 'Get the tags/categories associated with a workflow' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_workflow_tags safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_workflow_tags, this is the rule to start with:
get_workflow_tags is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every get_workflow_tags call is checked against it from then on.
Questions about get_workflow_tags
Get the tags/categories associated with a workflow. It is categorised as a Read tool in the FlowDot MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for get_workflow_tags: 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 FlowDot MCP Server. Nothing to install.
get_workflow_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_workflow_tags 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.
Set action: deny in the PolicyLayer policy for get_workflow_tags. 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.
get_workflow_tags is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue