update_data

Update records in memory.db table

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1999azzar-project-guardian-mcp-server/update-data.md

WHAT IT DOES

What update_data does on Project Guardian MCP

AI agents use update_data to create or update resources in Project Guardian MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Guardian MCP environment.

RISK

Why update_data is rated Medium

The tool updates (modifies) records in a SQLite database table, which is a reversible write operation. While it alters data, it does not irreversibly delete or destroy information (distinguishing it from Destructive tools like delete_data/delete_entity on the same server).

From the tool's definition Tool name 'update_data' and description 'Update records in memory.db table' indicate modification of existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_data safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_data, this is the rule to start with:

update_data Rate-limited

update_data 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_data": {
      "limits": [
        {
          "counter": "update_data_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Project Guardian MCP, apply this rule, and every update_data call is checked against it from then on.

FAQ

Questions about update_data

What does the update_data tool do? +

Update records in memory.db table. It is categorised as a Write tool in the Project Guardian MCP 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_data? +

Register the Project Guardian MCP server in PolicyLayer and add a rule for update_data: 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 Project Guardian MCP. Nothing to install.

What risk level is update_data? +

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

Can I rate-limit update_data? +

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

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

update_data is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Project Guardian, and thousands of servers like it.

This server

All 38 Project Guardian tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →