update_sender_profile
Rename one sender (From) or reply-to profile in place, without changing which profile is the account default. Use this to standardize a display name across the several identities a mailbox may carry, e.g. renaming
This record as markdown: /tools/io-github-polnikale-sequenzy-mcp/update-sender-profile.md
What update_sender_profile does on Sequenzy Mcp
AI agents use update_sender_profile 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 update_sender_profile is rated Medium
This tool updates sender profile metadata (display names, reply-to addresses) which is a reversible modification of account configuration data. It does not delete profiles (would be Destructive), execute external code (Execute), move funds (Financial), or merely read data (Read).
From the tool's definition Tool description states 'Rename one sender (From) or reply-to profile in place' — this modifies existing sender profile configuration without deletion or creation of new profiles.
Attacks that exploit this kind of access
The rule that runs update_sender_profile 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 update_sender_profile, this is the rule to start with:
update_sender_profile 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 update_sender_profile call is checked against it from then on.
Questions about update_sender_profile
Rename one sender (From) or reply-to profile in place, without changing which profile is the account default. Use this to standardize a display name across the several identities a mailbox may carry, e.g. renaming. 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 update_sender_profile: 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.
update_sender_profile 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 update_sender_profile 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 update_sender_profile. 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.
update_sender_profile 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