create_task_context · Task Context MCP Server MCP

WHAT IT DOES

What create_task_context does on Task Context MCP Server

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

WHY IT NEEDS A POLICY

Why create_task_context needs a policy

This tool creates new task contexts, which modifies the server's data store by adding records. This is a Write operation (reversible data creation). Severity is medium because creating task contexts could clutter the system or be misused to inject misleading task instructions that guide future agent behavior, but individual task contexts are not inherently destructive or financial in nature.

From the tool's definition Tool name 'create_task_context' combined with server description indicating it 'storing reusable task contexts with associated artifacts' indicates data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_task_context Rate-limited

create_task_context 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_context": {
      "limits": [
        {
          "counter": "create_task_context_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 Task Context MCP Server, so you can run agents against it safely.

FAQ

Questions about create_task_context

What does the create_task_context tool do? +

create_task_context. It is categorised as a Write tool in the Task Context 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_context? +

Register the Task Context MCP Server MCP server in PolicyLayer and add a rule for create_task_context: 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 Task Context MCP Server. Nothing to install.

What risk level is create_task_context? +

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

Can I rate-limit create_task_context? +

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

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

create_task_context is provided by the Task Context MCP Server MCP server (l0kifs/task-context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.