获取工作流配置 - 支持stage1/2/3/4/5阶段
AI agents call get_workflow_config to retrieve information from JoyCode MCP Server - FOP Workflow Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation to fetch workflow configuration parameters. There are no side effects, no code execution, no data modification, and no destructive operations. It is a passive query of existing configuration state, making it a clear Read category with low severity.
From the tool's definition Tool name 'get_workflow_config' with description '获取工作流配置' (Get workflow configuration) indicates a retrieval operation. The function retrieves configuration data for workflow stages without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_workflow_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JoyCode MCP Server - FOP Workflow Assistant, and nothing reaches the server without passing your rules. This is the rule we recommend for get_workflow_config:
{
"version": "1",
"default": "deny",
"tools": {
"get_workflow_config": {}
}
}get_workflow_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取工作流配置 - 支持stage1/2/3/4/5阶段. It is categorised as a Read tool in the JoyCode MCP Server - FOP Workflow Assistant MCP Server, which means it retrieves data without modifying state.
Register the JoyCode MCP Server - FOP Workflow Assistant MCP server in PolicyLayer and add a rule for get_workflow_config: 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 JoyCode MCP Server - FOP Workflow Assistant. Nothing to install.
get_workflow_config 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_config 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_config. 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_config is provided by the JoyCode MCP Server - FOP Workflow Assistant MCP server (shaun888/easy-workflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 JoyCode MCP Server - FOP Workflow Assistant tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 JoyCode MCP Server - FOP Workflow Assistant tools catalogued and risk-classified — across an index of 42,500+ MCP servers.