Delete a specific comment from a discussion
AI agents call smartsheet_delete_comment to permanently remove resources in Smartsheet MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a comment, which cannot be undone. This fits the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While comment deletion has a more limited blast radius than deleting entire sheets or workspaces, it is still a destructive operation.
From the tool's definition Tool name contains 'delete' and description states 'Delete a specific comment from a discussion' - this irreversibly removes data.
Documented attack patterns abuse exactly the kind of access smartsheet_delete_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Smartsheet MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smartsheet_delete_comment:
{
"version": "1",
"default": "deny",
"hide": [
"smartsheet_delete_comment"
]
} smartsheet_delete_comment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a specific comment from a discussion. It is categorised as a Destructive tool in the Smartsheet MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Smartsheet MCP Server MCP server in PolicyLayer and add a rule for smartsheet_delete_comment: 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 Smartsheet MCP Server. Nothing to install.
smartsheet_delete_comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the smartsheet_delete_comment 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 smartsheet_delete_comment. 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.
smartsheet_delete_comment is provided by the Smartsheet MCP Server MCP server (terilios/smartsheet-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Smartsheet MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Smartsheet MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.