Get relationships for a table
AI agents call quickbase_get_relationships to retrieve information from QuickBase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing relationship information from a QuickBase table. It has no side effects, creates no data, executes no operations, and cannot modify or delete anything. It is a straightforward read operation consistent with the Read category definition of 'retrieves or queries data; no side effects'.
From the tool's definition Tool name contains 'get' and description states 'Get relationships for a table' — purely retrieves relationship metadata with no modification or deletion.
Attacks that exploit this kind of access
Get relationships for a table. It is categorised as a Read tool in the QuickBase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QuickBase MCP Server MCP server in PolicyLayer and add a rule for quickbase_get_relationships: 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_get_relationships is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the quickbase_get_relationships 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_get_relationships. 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_get_relationships 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 →