send_feedback
Send feedback, bug report, or feature request to the Grabbit team. Use this when you encounter parsing failures, missing features, broken URLs, or have improvement suggestions. The team reads these to improve the product. Be specific about what went wrong and where.
This record as markdown: /tools/com-grabbitapp-grabblist/send-feedback.md
What send_feedback does on Grabblist
AI agents use send_feedback to create or update resources in Grabblist, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Grabblist environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | — | The URL where the issue occurred |
tool | string | — | The tool you were using when the issue occurred (e.g. add_item, search_saved) |
type | string | Yes | Type: bug (something broken), parsing_failure (price/title/image not extracted), feature_request (wishlist), feedback (general feedback) |
error | string | — | Error message you received, if any |
message | string | Yes | What happened or what you propose. Be specific — the team reads this. |
Parameters from the server's own tool schema.
Why send_feedback is rated Medium
An AI agent can call send_feedback faster than any human can review: one bad instruction and it creates or modifies resources in Grabblist by the hundred, each call as confident as the last.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs send_feedback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Grabblist, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_feedback, this is the rule to start with:
send_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Grabblist, apply this rule, and every send_feedback call is checked against it from then on.
Questions about send_feedback
Send feedback, bug report, or feature request to the Grabbit team. Use this when you encounter parsing failures, missing features, broken URLs, or have improvement suggestions. The team reads these to improve the product. Be specific about what went wrong and where. It is categorised as a Write tool in the Grabblist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
send_feedback accepts 5 parameters: url, tool, type, error, message. Required: type, message. The full parameter table on this page comes from the server's own tool schema.
Register the Grabblist MCP server in PolicyLayer and add a rule for send_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 Grabblist. Nothing to install.
send_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 send_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 send_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.
send_feedback is provided by the Grabblist MCP server (https://mcp.grabbitapp.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Grabblist, and thousands of servers like it.
This server
Across the catalogue