Adds a sheet to favorites
AI agents use add_sheet_to_favorites to create or update resources in Smartsheet MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smartsheet MCP Server environment.
This tool modifies user preferences (favorites list) reversibly—the action can be undone by removing the sheet from favorites. It does not retrieve sensitive data, execute code, destroy data, or commit financial obligations. It fits the Write category as a reversible data modification.
From the tool's definition Tool name 'add_sheet_to_favorites' and description 'Adds a sheet to favorites' indicate a metadata modification operation that creates or updates a user preference/favorite association without altering the underlying sheet data.
Attacks that exploit this kind of access
Adds a sheet to favorites. It is categorised as a Write tool in the Smartsheet MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smartsheet MCP Server MCP server in PolicyLayer and add a rule for add_sheet_to_favorites: 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.
add_sheet_to_favorites 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 add_sheet_to_favorites 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 add_sheet_to_favorites. 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.
add_sheet_to_favorites is provided by the Smartsheet MCP Server MCP server (thomaswtwrt/smar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →