Targetprocess

55 tools. 18 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

18 can modify or destroy data
37 read-only
55 tools total

Community server · catalogue entry verified 29/06/2026

How to control Targetprocess ↓

What Targetprocess exposes to your agents

Read (37) Write / Execute (17) Destructive / Financial (1)
Critical Risk

The most dangerous Targetprocess tools

18 of Targetprocess's 55 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Targetprocess

PolicyLayer is an MCP gateway — it sits between your AI agents and Targetprocess, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete_card_relation": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add_comment": {
    "limits": [
      {
        "counter": "add_comment_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_bug_comments": {
    "limits": [
      {
        "counter": "get_bug_comments_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Targetprocess — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON TARGETPROCESS →

Instant setup, no code required.

All 55 Targetprocess tools

WRITE 17 tools
Write add_comment Adds provided content as a comment to the specified tp card by id, e.g. 145789 Write add_comment_with_user Adds provided content as a comment to the specified tp card by id, e.g. 145789 and mentions the user in the co Write add_test_cases_to_test_plan Adds generated test cases to a test plan linked to a TP card (UserStory, Bug, or Feature). Write create_bug Create a new bug card that summarizes the problem in concise, descriptive manner answering questions Write create_bug_based_on_card Create a new bug card based on provided card id that summarizes the problem in concise, descriptive manner ans Write create_card_relation Create a relation between two TP cards (UserStory, Bug, Feature, etc.). The Master is the source of the Write create_epic Create a new Epic in Targetprocess. Write create_feature Create a new Feature in Targetprocess. Write create_formatted_user_story Create a new user story in Targetprocess with a structured, template-driven description. The description Write create_task Create a new task linked to a user story. Write create_test_plan Create a new test plan linked to a UserStory, Bug, or Feature. Name and Project are required by the API; Descr Write create_user_story Create a new user story in Targetprocess. Write update_bug Update a bug card with data proded from user input. NOTE: pass only the fields that user wants to update Write update_epic Update a Targetprocess Epic. Pass only the fields to change. Write update_user_story Update a user story card with data provided from user input. NOTE: pass only the fields that user wants Write update_user_story_state Update a user story card sub state with data provided from user input. CRITICAL WORKFLOW: Before calling t Write write_test_cases <step action>
READ 37 tools
Read get_bug_comments Get comments for a TP bug by its ID Read get_bug_content Get tp card (bug) content by specified id, e.g. 145789 Read get_bug_workflows Get all Targetprocess bug workflows Read get_card_current_status Get the EntityState, TeamState, and assigned teams for a TP card (UserStory, Bug, or Feature) by ID Read get_card_relations Get all relations (Dependency, Blocker, Relation, Link, Duplicate) for a TP card (UserStory, Bug, Feature, etc Read get_commit_message Returns the formatted commit message string for a given task or bug ID. Formats: - Task on a user story: Read get_current_releases Get current releases Read get_epic_content Get a Targetprocess Epic by ID, including its description, state, and progress. Read get_epic_features Get all Features belonging to a Targetprocess Epic. Read get_feature_user_stories Get user stories for a TP feature by its ID Read get_in_progress_tasks_and_bugs Get all Tasks and Bugs currently in Read get_logged_in_user Get logged in user Read get_my_time_logs Get recent time log entries submitted by me. Read get_not_covered_user_stories_in_feature Get user stories for a TP feature by its ID that are not covered by any tests Read get_process_workflows Get all Targetprocess process workflows Read get_processes Get all Targetprocess processes Read get_projects Get all Targetprocess projects Read get_relation_types Get all relation types available in this Targetprocess instance (id + name). Use this to find the correct rela Read get_release_bugs Get release bugs Read get_release_features Get release features Read get_release_open_bugs Get release active bugs (bugs that are not closed, done, passed, ready to deploy) Read get_release_open_user_stories Get release active user stories (user stories that are not closed, done, passed, ready to deploy) Read get_release_user_stories Get release user stories Read get_release_user_stories_with_description Get release user stories with description in the response. Note: this is slower than Read get_teams Get all Targetprocess teams Read get_teams_and_team_assignments Get all Targetprocess teams and team assignments Read get_user_by_id Get user by id Read get_user_story_bugs Get bugs linked to a TP user story by its ID Read get_user_story_comments Get comments for a TP user story by its ID Read get_user_story_content Get tp card (user story) content by specified id, e.g. 145789 Read get_user_story_test_cases Fetches a TP UserStory Linked Test Plan and fetches its Test Cases by provided card ID. Read get_user_story_workflows Get all Targetprocess user story workflows, with sub-states Read get_users Get all users Read list_my_bugs List Bugs assigned to me. Optionally filter by state. Read list_my_user_stories List User Stories assigned to me. Use this to get an overview of current work. Optionally filter by state. Read log_time Log time spent working on a Task, User Story, or Bug. Call this after completing a task or at the end of a wor Read search_tp_cards Searches TP cards (UserStories or Bugs) by keyword or phrase or partial keyphrase in Card Description e.g.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Targetprocess

Can an AI agent delete data through the Targetprocess MCP server? +

Yes. The Targetprocess server exposes 1 destructive tools including delete_card_relation. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Targetprocess? +

The Targetprocess server has 17 write tools including add_comment, add_comment_with_user, add_test_cases_to_test_plan. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Targetprocess.

How many tools does the Targetprocess MCP server expose? +

55 tools across 3 categories: Destructive, Read, Write. 37 are read-only. 18 can modify, create, or delete data.

How do I enforce a policy on Targetprocess? +

Register the Targetprocess MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Targetprocess tool call.

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

Instant setup, no code required.

55 Targetprocess tools catalogued and risk-classified — across an index of 43,000+ 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.