Skip to main content
Glama
Ansvar-Systems

Security Controls MCP Server

get_provision

Look up security controls mapped to any framework provision (e.g., ISO_27001, NIST_800_53) by law and article, or retrieve a specific SCF control directly.

Instructions

Look up the SCF controls mapped to a security-framework provision reference, or fetch one SCF control directly with law='SCF'. Examples: law='ISO_27001', article='6.1.1'; law='IEC_62443', article='SR 1.1'; law='SCF', article='GOV-01'. Accepts gateway framework keys (ISO_27001, ISO_27002, NIST_CSF, NIST_800_53, IEC_62443, PCI_DSS, SOC_2, CIS, CMMC, COBIT, HIPAA) or any SCF framework key from list_frameworks (e.g. 'iso_27001_2022'). A bare parent ref (e.g. '6.1') matches all sub-references ('6.1.1', '6.1.2', ...). Returns a JSON envelope {results, _meta} with per-item _citation metadata. Body text is always the SCF control catalog (CC BY-ND 4.0) — this server does not redistribute framework body text. Returns up to 10 controls (~150 tokens each).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lawYesFramework key: a gateway canonical key (e.g. ISO_27001, NIST_CSF), an SCF framework key from list_frameworks (e.g. 'iso_27001_2022'), or 'SCF' for a direct SCF control lookup.
articleYesProvision reference within the framework (e.g. '6.1.1', 'SR 1.1', 'AC-2'), or the SCF control ID (e.g. 'GOV-01') when law='SCF'.
jurisdictionNoAccepted for gateway compatibility; ignored — security frameworks are not jurisdiction-scoped.
Behavior4/5

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

With no annotations, the description fully carries the burden. It discloses that results are limited to 10 controls, body text is only the SCF catalog (CC license), and returns a JSON envelope with _citation metadata. No side effects are expected.

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 moderately long but every sentence adds value. It is front-loaded with the main purpose and examples, though could be slightly trimmed without losing clarity.

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 no output schema, the description explains the return format and limitations. It covers all key behavioral aspects for a lookup tool with 3 parameters.

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 description coverage is 100% so baseline is 3. The description adds value by providing framework key examples, explaining bare parent ref matching, and clarifying that jurisdiction is ignored.

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 it looks up SCF controls by framework provision reference or direct SCF control ID. It provides concrete examples and explains bare parent ref matching. This distinguishes it from sibling tools like get_control or search_controls.

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 examples for various framework keys and explains the jurisdiction parameter is ignored. It doesn't explicitly state when not to use this tool versus alternatives, but the examples make usage clear.

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/Ansvar-Systems/security-controls-mcp'

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