Medium Risk

set_prompts

Set the global prompts configuration with instructions, taskPrefix, and/or taskSuffix.\n\n

How to control set_prompts ↓

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

Medium Risk

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

Documented attack patterns abuse exactly the kind of access set_prompts gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and TaskFlow MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_prompts:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_prompts": {
      "limits": [
        {
          "counter": "set_prompts_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

set_prompts 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.

  1. Create a free account and register TaskFlow MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the set_prompts tool do? +

Set the global prompts configuration with instructions, taskPrefix, and/or taskSuffix.\n\n. It is categorised as a Write tool in the TaskFlow MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_prompts? +

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

What risk level is set_prompts? +

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

Can I rate-limit set_prompts? +

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

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

set_prompts is provided by the TaskFlow MCP server (pinkpixel-dev/taskflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TaskFlow MCP tool call.

Deterministic rules across all 23 TaskFlow MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

23 TaskFlow MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.