Create a new column on the specific Retable
AI agents use add_column to create or update resources in Retable MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Retable MCP Server environment.
This tool creates a new column in a database table, which is a reversible Write operation. While it modifies the table schema, the change can be undone by deleting the column (as evidenced by 'delete_column' existing as a sibling tool). Severity is medium because schema modifications can impact dependent queries and applications, but the impact is localized to a specific table and the operation is reversible.
From the tool's definition Tool name is 'add_column' and description states 'Create a new column on the specific Retable'. The verb 'Create' explicitly indicates data modification.
Attacks that exploit this kind of access
Create a new column on the specific Retable. It is categorised as a Write tool in the Retable MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Retable MCP Server MCP server in PolicyLayer and add a rule for add_column: 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 Retable MCP Server. Nothing to install.
add_column 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_column 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_column. 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_column is provided by the Retable MCP Server MCP server (retable-io/mcp-server). 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 →