AI agents call read_cell to retrieve information from Wps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves data from a spreadsheet cell without modifying, deleting, or executing any operations. It is a straightforward read operation that poses minimal security risk, as it only accesses existing data.
From the tool's definition Tool name is 'read_cell' and description states 'Read a cell value.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Read a cell value. It is categorised as a Read tool in the Wps MCP Server, which means it retrieves data without modifying state.
Register the Wps MCP server in PolicyLayer and add a rule for read_cell: 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 Wps. Nothing to install.
read_cell 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 read_cell 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 read_cell. 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.
read_cell is provided by the Wps MCP server (xiao-rx/wps-mcp-server). 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 →