Skip to main content
Glama
Atlasent

atlasent-mcp

Official
by Atlasent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

AtlaSent — Create Policy

atlasent_create_policy

Create a draft policy bundle with ordered rules to define access control or approval requirements before publishing.

Instructions

Create a new constraint bundle for an action. The bundle starts in 'draft' status — call update_policy to publish it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rulesYesOrdered list of rules — first match wins.
titleYesHuman-readable policy title.
org_idYesOrganization ID that will own the policy.
actionsNoAction-specific configuration.
versionNoSemantic version string (e.g. '1.0.0').
priorityNoEvaluation priority (lower number = higher priority).
policy_idYesClient-assigned unique ID for this policy bundle (e.g. 'production-change').
applies_toNoScope selector controlling which requests this policy applies to.
expires_atNoISO-8601 timestamp when the policy expires.
descriptionNoOptional human-readable description.
policy_typeYesPolicy type (e.g. 'access_control', 'approval_gate').
effective_atNoISO-8601 timestamp when the policy becomes effective.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.12.2
    • changedInput schema / properties / policy_id / description
      Previous value: -"Client-assigned unique ID for this policy bundle (e.g. 'deploy-gate')."New value: +"Client-assigned unique ID for this policy bundle (e.g. 'production-change')."
  2. First observedv2.11.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only mark the tool as non-read-only and non-destructive; the description adds real behavior: a newly created policy is not immediately active — it is in draft and requires a later update_policy call to become published. This materially changes how an agent should reason about the effects of calling create.

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

Conciseness5/5

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

Two short sentences with no filler. The core action and the lifecycle caveat are both front-loaded, and the second sentence earns its place by naming the follow-up tool.

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

Completeness3/5

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

Despite the helpful lifecycle note, this is a 12-parameter creation tool with nested, loosely specified objects (rules, actions, applies_to) and no output schema. The description doesn't explain response behavior, duplicate-handling, or the structure expected inside the nested objects, so an agent is left to infer those from sparse schema entries.

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

Parameters3/5

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

All 12 parameters already have individual descriptions in the input schema, so the dimension baseline is 3. The tool description adds no parameter-level meaning beyond that; the schema carries the burden successfully.

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?

States a specific verb ('Create') and resource ('constraint bundle') and immediately orients the agent to the policy lifecycle by noting the new bundle starts in 'draft' status. It also distinguishes this creation tool from the sibling update_policy, since publishing is explicitly assigned to that tool.

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

Usage Guidelines4/5

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

The description gives the main routing signal: use this tool to create a new bundle, and call update_policy to publish it. It doesn't enumerate all siblings (list/get/delete), but for a create operation the create-vs-update distinction is the critical one and is explicit.

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

Deploy Server

Other Tools