High Risk →

task

Returns a task-focused system prompt that reminds the model to run npm-i-checker for installs and code-checker on code before replying.

Part of the E18e server.

task can trigger actions in E18e, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE E18E →

Free to start. No card required.

AI agents invoke task to trigger processes or run actions in E18e. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

task can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "task": {
      "limits": [
        {
          "counter": "task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full E18e policy for all 3 tools.

Get this rule live on your own E18e server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY E18E →

These attack patterns abuse exactly the kind of access task gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so task only ever does what you allow.

SECURE E18E →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the task tool do? +

Returns a task-focused system prompt that reminds the model to run npm-i-checker for installs and code-checker on code before replying.. It is categorised as a Execute tool in the E18e MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on task? +

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

What risk level is task? +

task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit task? +

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

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

task is provided by the E18e MCP server (@e18e/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every E18e tool call.

Deterministic rules across all 3 E18e tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.