Create a new row record in worksheet
AI agents use add_worksheet_record to create or update resources in HAP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HAP MCP Server environment.
This tool creates new records in a worksheet, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). While it modifies data, the action can be undone by deleting the record. Severity is medium because bulk misuse could fill a worksheet with unwanted records, but the impact is limited to a single worksheet and the data is recoverable.
From the tool's definition Tool name 'add_worksheet_record' and description 'Create a new row record in worksheet' indicate data creation and modification.
Attacks that exploit this kind of access
Create a new row record in worksheet. It is categorised as a Write tool in the HAP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HAP MCP Server MCP server in PolicyLayer and add a rule for add_worksheet_record: 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 HAP MCP Server. Nothing to install.
add_worksheet_record 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_worksheet_record 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_worksheet_record. 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_worksheet_record is provided by the HAP MCP Server MCP server (mingdaocloud/hap-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 →