update_record

Update fields on an existing record.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/update-record.md

WHAT IT DOES

What update_record does on ProAgentStore

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

RISK

Why update_record is rated Medium

This tool creates or modifies data in a reversible manner, fitting the Write category definition. It is not destructive since updates can typically be reverted. The severity is medium because misuse could corrupt or alter important records in the ProAgentStore control plane, but the impact is typically reversible. Confidence is high based on explicit 'Update' language in the description.

From the tool's definition Tool description states 'Update fields on an existing record.' The verb 'Update' and the phrase 'on an existing record' clearly indicate this tool modifies data reversibly without deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_record safely

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

update_record Rate-limited

update_record 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_record": {
      "limits": [
        {
          "counter": "update_record_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 ProAgentStore, apply this rule, and every update_record call is checked against it from then on.

FAQ

Questions about update_record

What does the update_record tool do? +

Update fields on an existing record. It is categorised as a Write tool in the ProAgentStore 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_record? +

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

What risk level is update_record? +

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

Can I rate-limit update_record? +

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

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

update_record is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore 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 →