pipeworx_feedback

SERVER19hz SOURCEhttps://gateway.pipeworx.io/19hz/mcp

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pipeworx-io-19hz/pipeworx-feedback.md

WHAT IT DOES

What pipeworx_feedback does on 19hz

AI agents use pipeworx_feedback to create or update resources in 19hz, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 19hz 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.

RISK

Why pipeworx_feedback is rated Medium

This tool submits feedback (bug reports, feature requests, praise) to the Pipeworx team. It creates/posts data (feedback records) to an external system, making it a Write operation. The blast radius is low — misuse could spam the feedback system but is rate-limited to 5/day and has no destructive or financial consequences.

From the tool's definition Tell the Pipeworx team something is broken, missing, or needs to exist... signal directly affects roadmap. Rate-limited to 5 per identifier per day.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pipeworx_feedback safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 19hz, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipeworx_feedback, this is the rule to start with:

pipeworx_feedback Rate-limited

pipeworx_feedback 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": {
    "pipeworx_feedback": {
      "limits": [
        {
          "counter": "pipeworx_feedback_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 19hz, apply this rule, and every pipeworx_feedback call is checked against it from then on.

FAQ

Questions about pipeworx_feedback

What does the pipeworx_feedback tool do? +

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 19hz MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does pipeworx_feedback accept? +

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.

How do I enforce a policy on pipeworx_feedback? +

Register the 19hz 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 19hz. Nothing to install.

What risk level is pipeworx_feedback? +

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

Can I rate-limit pipeworx_feedback? +

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.

How do I block pipeworx_feedback completely? +

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.

What MCP server provides pipeworx_feedback? +

pipeworx_feedback is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 19hz, and thousands of servers like it.

This server

All 32 19hz tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →