Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

create_snowflake_access_policy

Define and enforce access rules for Snowflake databases, specifying which roles can read or write to specific schemas and tables, with optional scheduling.

Instructions

Create an access management policy for a Snowflake datasource.

Defines which roles can access which databases, schemas, or tables with read or write permissions. Policies are enforced by ALTR and checked on a schedule.

Each rule in the list must contain:

  • actors: list of dicts with 'type' ("role"), 'condition' ("equals"|"starts_with"|"ends_with"), and 'identifiers' (list of str).

  • objects: list of dicts with 'type' ("database"|"schema"|"table"), 'condition' ("equals"|"starts_with"|"ends_with"| "fully_qualified"), and 'identifiers' (list of str) or 'fully_qualified_identifiers' (list of dicts with database/schema/table/view keys).

  • access: list of dicts with 'name' ("read"|"write").

Optionally, rules may include 'tagged_objects' for tag-based targeting:

  • tagged_objects: list of dicts with 'check_against' (list of "databases"|"schemas"|"tables"|"views"), 'tagged_with' (list of dicts with database/schema/name/value keys), and 'tag_condition' ("or"|"and").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
policy_nameYesName for the policy (1-255 chars).
descriptionYesDescription of the policy (1-255 chars).
connection_idYesALTR connection ID for the Snowflake database.
rulesYesList of access rule objects, or a JSON string encoding such a list.
policy_maintenanceNoOptional schedule dict with 'rate' ("day"|"cron") and 'value' (number or cron string).
access_request_idNoOptional access request ID this policy fulfills.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It details the rule structure but omits behavioral aspects like immediate enforcement, permissions required, or whether creation overrides existing policies. Basic context is given but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear first sentence and detailed bullet points for rules. It is not overly verbose, though some redundancy exists (e.g., repeating 'list of dicts' pattern could be more concise).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists and parameters have 100% coverage, the description covers the essential purpose and the complex rule structure. It lacks details on error cases or output format, but the presence of an output schema mitigates that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing a baseline of 3. The description adds significant value for the complex 'rules' parameter by specifying required fields (actors, objects, access, tagged_objects) and their subtypes, which is beyond the schema's generic 'list of objects' definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a Snowflake access policy and specifies its components (roles, objects, access). It distinguishes itself from siblings like create_oltp_access_policy and update_snowflake_access_policy by targeting Snowflake datasources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the policy does (enforced by ALTR, scheduled checks) but does not explicitly compare to alternatives like create_oltp_access_policy or update_snowflake_access_policy. It lacks guidance on when to use this tool vs others.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/altrsoftware/altr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server