Add a new record to a parquet file. Creates audit log entry and optionally creates full snapshot based on configuration. Use only when a rule or workflow requires Parquet (e.g. per .cursor/rules/neotoma_parquet_migration.mdc write to Neotoma first; then if the data type still uses Parquet, also w...
AI agents use add_record to create or update resources in Parquet MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Parquet MCP Server environment.
This tool creates new records in a Parquet file, which is a Write operation—it modifies data reversibly. While it does create audit logs (good practice), the core function is data creation/insertion, not deletion or irreversible destruction. The mention of 'rollback_operation' as a sibling capability confirms that write operations here are meant to be reversible.
From the tool's definition Tool description states 'Add a new record to a parquet file' and 'Creates audit log entry'. The tool performs record creation which is a reversible modification operation.
Attacks that exploit this kind of access
Add a new record to a parquet file. Creates audit log entry and optionally creates full snapshot based on configuration. Use only when a rule or workflow requires Parquet (e.g. per .cursor/rules/neotoma_parquet_migration.mdc write to Neotoma first; then if the data type still uses Parquet, also write via this tool). Check for existing records first to avoid duplicates. It is categorised as a Write tool in the Parquet MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Parquet MCP Server MCP server in PolicyLayer and add a rule for add_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 Parquet MCP Server. Nothing to install.
add_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 add_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 add_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.
add_record is provided by the Parquet MCP Server MCP server (markmhendrickson/mcp-server-parquet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →