Low Risk

get_output_directories

获取输出目录配置 - 返回所有输出目录路径

How to control get_output_directories ↓

AI agents call get_output_directories 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.

Low Risk

This is a read-only tool that retrieves configuration information about output directories. It has no side effects, does not execute code, does not modify data, and does not delete anything. The 'get_' prefix and the retrieval nature of the operation confirm it is a Read category tool with low severity, as unauthorized access to directory paths poses minimal risk compared to other operation types.

From the tool's definition Tool name 'get_output_directories' and description '获取输出目录配置 - 返回所有输出目录路径' (Get output directory configuration - return all output directory paths) indicate a retrieval operation that queries configuration data without modifying it.

Documented attack patterns abuse exactly the kind of access get_output_directories 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_output_directories:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_output_directories": {}
  }
}

get_output_directories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register JoyCode MCP Server - FOP Workflow Assistant — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_output_directories tool do? +

获取输出目录配置 - 返回所有输出目录路径. 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.

How do I enforce a policy on get_output_directories? +

Register the JoyCode MCP Server - FOP Workflow Assistant MCP server in PolicyLayer and add a rule for get_output_directories: 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.

What risk level is get_output_directories? +

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

Can I rate-limit get_output_directories? +

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

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

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

Enforce policy on every JoyCode MCP Server - FOP Workflow Assistant tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.