submit_feedback
Send product feedback about Sequenzy itself to the Sequenzy team. IMPORTANT: call this tool whenever the user wanted to accomplish something and Sequenzy did not expose functionality for it - a missing tool or argument, an unsupported workflow, a confusing behavior, or a bug. When something you d...
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/submit-feedback.md
What submit_feedback does on Sequenzy Mcp
AI agents use submit_feedback to create or update resources in Sequenzy Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sequenzy Mcp environment.
Why submit_feedback is rated Medium
Creates feedback records with no side effects on email marketing operations or data.
From the tool's definition Send product feedback about Sequenzy itself to the Sequenzy team.
Attacks that exploit this kind of access
The rule that runs submit_feedback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sequenzy Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_feedback, this is the rule to start with:
submit_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 Sequenzy Mcp, apply this rule, and every submit_feedback call is checked against it from then on.
Questions about submit_feedback
Send product feedback about Sequenzy itself to the Sequenzy team. IMPORTANT: call this tool whenever the user wanted to accomplish something and Sequenzy did not expose functionality for it - a missing tool or argument, an unsupported workflow, a confusing behavior, or a bug. When something you did through these tools produced a wrong or unexpected result, also fill in userIntent, toolCalls, expected, actual, and resourceIds so the team can reproduce it. Summarize tool arguments instead of pasting raw subscriber data, and never include secrets or API keys. Briefly tell the user you reported the gap. This feedback goes straight to the team and shapes what gets built next. Do not use it for questions about the user. It is categorised as a Write tool in the Sequenzy Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sequenzy MCP server in PolicyLayer and add a rule for submit_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 Sequenzy Mcp. Nothing to install.
submit_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 submit_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 submit_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.
submit_feedback is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sequenzy, and thousands of servers like it.
This server
Across the catalogue