Skip to main content
Glama

Set a security policy key

security_set
Idempotent

Set security and policy settings (allow/deny, tool lists, CSP origins) for reserved keys that generic data tools refuse. Validates values, rejecting unknown input.

Instructions

Privileged writer for reserved settings keys (security:* / policy:) — the ONLY tool that can write them; the generic data_ tools refuse reserved keys. Upserts one key/value in the settings collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesa reserved key, e.g. security:kanban:send_message (cap suffixes are snake_case — the caps field names)
valueYesthe policy value: allow | deny (true/false too); delete_items also takes confirm; call_tools takes "*", a JSON array or a comma-separated tool list; policy:csp:<app> (or policy:csp:*) takes a JSON object of origin arrays, e.g. {"connectDomains":["https://api.example.com"]}. An unknown value is REFUSED, never stored
command_idNoidempotency key (uuid); auto-generated if omitted

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
okYes
eotNo
seqNo
itemNo
noteNo
reasonNo
deletedNo
collectionNo
violationsNo
expected_versionNo
prev_collection_seqNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / value / description
      Previous value: -"the policy value: allow | deny (true/false too); delete_items also takes confirm; call_tools takes \"*\", a JSON array or a comma-separated tool list. An unknown value is REFUSED, never stored"New value: +"the policy value: allow | deny (true/false too); delete_items also takes confirm; call_tools takes \"*\", a JSON array or a comma-separated tool list; policy:csp:<app> (or policy:csp:*) takes a JSON object of origin arrays, e.g. {\"connectDomains\":[\"https://api.example.com\"]}. An unknown value is REFUSED, never stored"
  2. First observedv0.5.7

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover idempotency and non-destructiveness; the description adds the privileged-auth requirement, the reserved-key restriction, and the upsert semantics in the settings collection. This goes beyond the structured annotations without contradicting them.

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 dense sentences carry the core purpose, exclusivity, and write behavior. The most important differentiator ('the ONLY tool that can write them') is front-loaded, with no filler.

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

Completeness5/5

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

Given the rich schema, an output schema, and annotations, the description provides the essential contextual framing: target keys, elevated privileges, exclusivity, and upsert behavior. Nothing needed for correct selection or invocation is missing.

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?

Schema description coverage is 100%, and the schema itself provides detailed parameter semantics for key, value, and command_id. The tool description does not add parameter-level meaning, but with full schema coverage it does not need to.

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 ('Privileged writer') and precise resource scope ('reserved settings keys (security:* / policy:*)'), and explicitly differentiates from the generic data_* tools. An agent can immediately understand both what it does and how it is distinct.

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

Usage Guidelines5/5

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

Explicitly names the alternative family (data_* tools) and explains the exclusion: data_* tools refuse reserved keys, so security_set is the ONLY writer for these keys. This gives the agent a clear routing rule.

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

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/2nd1st/open-mcp-apps'

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