AI agents call get_flow_roles to retrieve information from MCP Feishu Project Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite an empty description, the naming pattern and context of sibling tools indicate this retrieves workflow role information from the Feishu project management system. No side effects, modifications, deletions, or financial transactions are implied. Confidence is moderate (0.7) due to the missing description, but the 'get_' prefix and server purpose strongly suggest a read operation.
From the tool's definition Tool name 'get_flow_roles' suggests retrieval of role information; sibling tools on this server (get_view_detail, get_view_list, get_work_item_detail) are all read operations that retrieve project data without modification.
Documented attack patterns abuse exactly the kind of access get_flow_roles gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Feishu Project Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for get_flow_roles:
{
"version": "1",
"default": "deny",
"tools": {
"get_flow_roles": {}
}
}get_flow_roles 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.
get_flow_roles. It is categorised as a Read tool in the MCP Feishu Project Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Feishu Project Manager MCP server in PolicyLayer and add a rule for get_flow_roles: 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 MCP Feishu Project Manager. Nothing to install.
get_flow_roles 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_flow_roles 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_flow_roles. 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_flow_roles is provided by the MCP Feishu Project Manager MCP server (roland0511/mcp-feishu-proj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Feishu Project Manager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Feishu Project Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.