create_task · PocketBase Task MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_task does on PocketBase Task MCP Server

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

WHY IT NEEDS A POLICY

Why create_task needs a policy

This tool creates new records in the database, modifying the application state. The blast radius is moderate—a compromised agent could generate spurious tasks and consume storage, but the operation is reversible (tasks can be deleted). It does not execute arbitrary code, delete data, or move funds, so Write is the appropriate category with medium severity.

From the tool's definition Tool explicitly creates a new task in PocketBase ('Create a new task in the local PocketBase'), which is a reversible write operation. The name 'create_task' and description clearly indicate data creation.

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 PocketBase Task MCP Server, 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 the local PocketBase. It is categorised as a Write tool in the PocketBase Task MCP Server 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 PocketBase Task MCP Server 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 PocketBase Task MCP Server. 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 PocketBase Task MCP Server MCP server (muhammadchhota/mcp-demo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.