Low Risk

lark_get_task_status

查询异步任务状态

How to control lark_get_task_status ↓

What lark_get_task_status does on Feishu Enhance

AI agents call lark_get_task_status to retrieve information from Feishu Enhance without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why lark_get_task_status needs a policy

This tool retrieves the status of existing async tasks without modifying, executing, or deleting anything. It is purely informational and poses minimal security risk—an agent could only learn the state of tasks that already exist. No side effects, financial impact, or destructive capabilities are present.

From the tool's definition Tool name and description indicate a query operation: 'get_task_status' (retrieves state) and '查询异步任务状态' (Chinese: 'query async task status'). The description explicitly uses '查询' (query/check), a read-only verb.

Documented attack patterns abuse exactly the kind of access lark_get_task_status gives an agent:

How to control lark_get_task_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Feishu Enhance, and nothing reaches the server without passing your rules. This is the rule we recommend for lark_get_task_status:

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

lark_get_task_status 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 Feishu Enhance — 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.

Related tools and policies

Go deeper

Questions about lark_get_task_status

What does the lark_get_task_status tool do? +

查询异步任务状态. It is categorised as a Read tool in the Feishu Enhance MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lark_get_task_status? +

Register the Feishu Enhance MCP server in PolicyLayer and add a rule for lark_get_task_status: 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 Feishu Enhance. Nothing to install.

What risk level is lark_get_task_status? +

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

Can I rate-limit lark_get_task_status? +

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

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

lark_get_task_status is provided by the Feishu Enhance MCP server (jiaxinghit/feishu-enhance-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Feishu Enhance tool call.

Start from Feishu Enhance, 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.

24 Feishu Enhance tools catalogued and risk-classified — across an index of 43,000+ 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.