update_story_or_task · TAPD MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_story_or_task does on TAPD MCP Server

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

WHY IT NEEDS A POLICY

Why update_story_or_task needs a policy

This tool creates or modifies data reversibly within an agile project management system. While the description is empty and lacks specificity about scope, the naming pattern and sibling tools (create_story_or_task, create_bug, create_comments) establish context that this operates on editable project artifacts.

From the tool's definition Tool name 'update_story_or_task' indicates modification of project management entities (stories/tasks) within the TAPD agile platform. The 'update' verb reflects reversible changes to existing data structures used in project tracking.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_story_or_task Rate-limited

update_story_or_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": {
    "update_story_or_task": {
      "limits": [
        {
          "counter": "update_story_or_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 TAPD MCP Server, so you can run agents against it safely.

FAQ

Questions about update_story_or_task

What does the update_story_or_task tool do? +

update_story_or_task. It is categorised as a Write tool in the TAPD 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 update_story_or_task? +

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

What risk level is update_story_or_task? +

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

Can I rate-limit update_story_or_task? +

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

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

update_story_or_task is provided by the TAPD MCP Server MCP server (ken19990709/mcp-server-for-tapd). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.