Retrieves the history of changes for a specific cell
AI agents call get_cell_history to retrieve information from Smartsheet MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data (cell change history) with no side effects, modifications, deletions, or external operations. It is a straightforward data retrieval function consistent with the 'Read' category. Severity is low because accessing historical metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_cell_history' and description 'Retrieves the history of changes for a specific cell' indicate a read-only query operation that accesses historical data without modification.
Attacks that exploit this kind of access
Retrieves the history of changes for a specific cell. It is categorised as a Read tool in the Smartsheet MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smartsheet MCP Server MCP server in PolicyLayer and add a rule for get_cell_history: 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.
get_cell_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_cell_history 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 get_cell_history. 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.
get_cell_history 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 →