Get operation logs for a specific row record
AI agents call get_worksheet_record_logs to retrieve information from HAP 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 audit/operation logs for a worksheet record, which is a read-only operation with no side effects. It does not create, modify, delete, or execute code. The blast radius of misuse is minimal—an agent could over-query logs or access logs it shouldn't have permission for, but cannot alter data or trigger external operations.
From the tool's definition Tool name contains 'get' and description states 'Get operation logs for a specific row record' — a query operation that retrieves historical log data without modifying or deleting anything.
Attacks that exploit this kind of access
Get operation logs for a specific row record. It is categorised as a Read tool in the HAP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HAP MCP Server MCP server in PolicyLayer and add a rule for get_worksheet_record_logs: 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.
get_worksheet_record_logs 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_worksheet_record_logs 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_worksheet_record_logs. 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_worksheet_record_logs 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 →