create_task · Tyme MCP: Risk & Policy

WHAT IT DOES

What create_task does on Tyme

AI agents use create_task to create or update resources in Tyme — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tyme environment.

WHY IT NEEDS A POLICY

Why create_task needs a policy

An AI agent can call create_task faster than any human can review — one bad instruction and it creates or modifies resources in Tyme by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_task Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_task": {
      "limits": [
        {
          "counter": "create_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tyme, so you can run agents against it safely.

FAQ

Questions about create_task

What does the create_task tool do? +

Create a new task in a project. It is categorised as a Write tool in the Tyme MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_task? +

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

What risk level is create_task? +

create_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_task? +

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

How do I block create_task completely? +

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

What MCP server provides create_task? +

create_task is provided by the Tyme MCP server (watarutmnh/tyme-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.