Create a lookup field to pull data from a related table
AI agents use quickbase_create_lookup_field to create or update resources in QuickBase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuickBase MCP Server environment.
The tool creates a new lookup field in a QuickBase table, which is a reversible write operation that modifies database schema. While it doesn't directly modify existing data, creating a field is a structural change that can be undone by deleting the field.
From the tool's definition Tool description states 'Create a lookup field' which is a data creation operation. The sibling tools include destructive operations (quickbase_delete_field, quickbase_delete_record, quickbase_delete_table) and write operations (quickbase_create_field,…
Attacks that exploit this kind of access
Create a lookup field to pull data from a related table. It is categorised as a Write tool in the QuickBase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QuickBase MCP Server MCP server in PolicyLayer and add a rule for quickbase_create_lookup_field: 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 QuickBase MCP Server. Nothing to install.
quickbase_create_lookup_field 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 quickbase_create_lookup_field 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 quickbase_create_lookup_field. 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.
quickbase_create_lookup_field is provided by the QuickBase MCP Server MCP server (lawrencecirillo/quickbase-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 →