AI agents use feishu_create_task to create or update resources in autoMate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your autoMate environment.
The tool creates a new task record in Feishu, which is a reversible write operation. While the description is absent (lowering confidence), the naming pattern aligns with sibling tools like 'airtable_create_record' and 'asana_create_task' on the same server, all of which are Write category.
From the tool's definition Tool name 'feishu_create_task' indicates creation of a task in Feishu (a collaboration platform); the 'create' verb signals a write operation that generates new data. Description is empty, reducing confidence.
Documented attack patterns abuse exactly the kind of access feishu_create_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for feishu_create_task:
{
"version": "1",
"default": "deny",
"tools": {
"feishu_create_task": {
"limits": [
{
"counter": "feishu_create_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}feishu_create_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
feishu_create_task. It is categorised as a Write tool in the autoMate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the autoMate MCP server in PolicyLayer and add a rule for feishu_create_task: 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 autoMate. Nothing to install.
feishu_create_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the feishu_create_task 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 feishu_create_task. 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.
feishu_create_task is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.