AI agents call yfy_get_department_info to retrieve information from Yifangyun without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves department metadata using a token, which is a read-only query operation. It does not create, modify, delete, execute code, or commit financial transactions. The worst-case misuse would be unauthorized information disclosure about organizational structure, which is low severity in the confidentiality dimension but carries no integrity or availability risk.
From the tool's definition Tool name 'yfy_get_department_info' and description 'Get department metadata' indicate a retrieval operation with no modification capability.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get department metadata using the enterprise token. Use department_id=0 for the root department when supported by the deployment. It is categorised as a Read tool in the Yifangyun MCP Server, which means it retrieves data without modifying state.
Register the Yifangyun MCP server in PolicyLayer and add a rule for yfy_get_department_info: 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 Yifangyun. Nothing to install.
yfy_get_department_info 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 yfy_get_department_info 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 yfy_get_department_info. 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.
yfy_get_department_info is provided by the Yifangyun MCP server (mrhegit/yifangyun-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →