insert_record
Insert a new record into a collection.
This record as markdown: /tools/io-github-proagentstore-platform/insert-record.md
What insert_record does on ProAgentStore
AI agents use insert_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.
Why insert_record is rated Medium
This tool creates new records in a collection, which is a reversible write operation. It does not execute arbitrary code, delete data irreversibly, or move money. The 'medium' severity reflects that unintended record insertion could corrupt data or cause application issues, but the operation is reversible via deletion or updates.
From the tool's definition Tool name 'insert_record' and description 'Insert a new record into a collection' indicate creation of new data.
Attacks that exploit this kind of access
The rule that runs insert_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 insert_record, this is the rule to start with:
insert_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.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every insert_record call is checked against it from then on.
Questions about insert_record
Insert a new record into a collection. 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.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for insert_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.
insert_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the insert_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.
Set action: deny in the PolicyLayer policy for insert_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.
insert_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.
More on ProAgentStore, and thousands of servers like it.
This server
Across the catalogue