Low Risk

numbers_read_cell

Read a single cell

How to control numbers_read_cell ↓

What numbers_read_cell does on Iwork

AI agents call numbers_read_cell to retrieve information from Iwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why numbers_read_cell needs a policy

This tool retrieves cell data from a Numbers spreadsheet with no side effects. It performs a simple query operation characteristic of Read category tools. The low severity reflects minimal blast radius—reading spreadsheet cells poses no risk of data loss, financial impact, or system damage.

From the tool's definition Tool name 'numbers_read_cell' and description 'Read a single cell' explicitly indicate data retrieval without modification.

Documented attack patterns abuse exactly the kind of access numbers_read_cell gives an agent:

How to control numbers_read_cell

PolicyLayer is an MCP gateway — it sits between your AI agents and Iwork, and nothing reaches the server without passing your rules. This is the rule we recommend for numbers_read_cell:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "numbers_read_cell": {}
  }
}

numbers_read_cell is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Iwork — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about numbers_read_cell

What does the numbers_read_cell tool do? +

Read a single cell. It is categorised as a Read tool in the Iwork MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on numbers_read_cell? +

Register the Iwork MCP server in PolicyLayer and add a rule for numbers_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 Iwork. Nothing to install.

What risk level is numbers_read_cell? +

numbers_read_cell is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit numbers_read_cell? +

Yes. Add a rate_limit block to the numbers_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.

How do I block numbers_read_cell completely? +

Set action: deny in the PolicyLayer policy for numbers_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.

What MCP server provides numbers_read_cell? +

numbers_read_cell is provided by the Iwork MCP server (reichenbach/iwork_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Iwork tool call.

Start from Iwork, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

114 Iwork tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.