update_reference_list_row

WHAT IT DOES

What update_reference_list_row does on ReliaQuest GreyMatter MCP Server

AI agents use update_reference_list_row to create or update resources in ReliaQuest GreyMatter MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReliaQuest GreyMatter MCP Server environment.

WHY IT NEEDS A POLICY

Why update_reference_list_row needs a policy

This tool updates rows in reference lists, which is a reversible modification of data. While it modifies data (Write severity), it is not destructive (deletion/purge), does not execute arbitrary code or commands (would be Execute), and does not involve financial transactions (would be Financial).

From the tool's definition Tool name 'update_reference_list_row' combined with 'mutation updateReferenceListRow' directly indicates a write operation that modifies data in reference lists. The GraphQL mutation pattern confirms this creates or modifies data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_reference_list_row Rate-limited

update_reference_list_row stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_reference_list_row": {
      "limits": [
        {
          "counter": "update_reference_list_row_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ReliaQuest GreyMatter MCP Server, so you can run agents against it safely.

FAQ

Questions about update_reference_list_row

What does the update_reference_list_row tool do? +

Reference Lists \u00b7 mutation updateReferenceListRow. Variables: input. Example variables: {\. It is categorised as a Write tool in the ReliaQuest GreyMatter MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_reference_list_row? +

Register the ReliaQuest GreyMatter MCP Server MCP server in PolicyLayer and add a rule for update_reference_list_row: 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 ReliaQuest GreyMatter MCP Server. Nothing to install.

What risk level is update_reference_list_row? +

update_reference_list_row is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_reference_list_row? +

Yes. Add a rate_limit block to the update_reference_list_row 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 update_reference_list_row completely? +

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

update_reference_list_row is provided by the ReliaQuest GreyMatter MCP Server MCP server (space-c0wboy/reliaquest-greymatter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.