Query records using a structured SmartSuite filter. Use smartsuite_describe_application first to learn field slugs and valid values for choice fields.
AI agents call smartsuite_query_records to retrieve information from SmartSuite MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from SmartSuite records without creating, modifying, deleting, or executing operations. Query operations are read-only with no side effects, fitting the Read category. Severity is low because the blast radius of misuse is limited to unauthorized data access, mitigated by the server's configurable access modes and audit logging mentioned in the server description.
From the tool's definition Tool name 'query_records' and description 'Query records using a structured SmartSuite filter' indicate data retrieval with no modification. The guidance to 'use smartsuite_describe_application first' suggests introspection for querying, not mutation.
Attacks that exploit this kind of access
Query records using a structured SmartSuite filter. Use smartsuite_describe_application first to learn field slugs and valid values for choice fields. It is categorised as a Read tool in the SmartSuite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SmartSuite MCP Server MCP server in PolicyLayer and add a rule for smartsuite_query_records: 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 SmartSuite MCP Server. Nothing to install.
smartsuite_query_records 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 smartsuite_query_records 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 smartsuite_query_records. 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.
smartsuite_query_records is provided by the SmartSuite MCP Server MCP server (smartsuitefoundry/smartsuite-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 →