Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — ...
AI agents use pipeworx_feedback to create or update resources in Mcp Mydisease — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mydisease environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | bug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = |
context | object | — | Optional structured context: which tool, pack, or vertical this relates to. |
message | string | Yes | Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max. |
Parameters from the server's own tool schema.
This tool submits feedback to an external team, which constitutes creating/writing data (a feedback record) on a remote system. It has no destructive, financial, or execution capabilities. Misuse could result in spam or misleading roadmap signals, but blast radius is low given rate-limiting and the benign nature of feedback submission.
From the tool's definition Tell the Pipeworx team something is broken, missing, or needs to exist... The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day.
Attacks that exploit this kind of access
Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota. It is categorised as a Write tool in the Mcp Mydisease MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
pipeworx_feedback accepts 3 parameters: type, context, message. Required: type, message. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Mydisease MCP server in PolicyLayer and add a rule for pipeworx_feedback: 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 Mcp Mydisease. Nothing to install.
pipeworx_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pipeworx_feedback 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.
Set action: deny in the PolicyLayer policy for pipeworx_feedback. 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.
pipeworx_feedback is provided by the Mcp Mydisease MCP server (https://gateway.pipeworx.io/mydisease/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →