Semiotic

16 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated:

3 can modify or destroy data
13 read-only
16 tools total

Community server · catalogue entry verified 26/06/2026

How to control Semiotic ↓

What Semiotic exposes to your agents

Read (13) Write / Execute (3) Destructive / Financial (0)
High Risk

The most dangerous Semiotic tools

3 of Semiotic's 16 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Semiotic

PolicyLayer is an MCP gateway — it sits between your AI agents and Semiotic, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "reportIssue": {
    "limits": [
      {
        "counter": "reportissue_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "applyTheme": {
    "limits": [
      {
        "counter": "applytheme_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Semiotic — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON SEMIOTIC →

Instant setup, no code required.

All 16 Semiotic tools

READ 13 tools
Read applyTheme Get usage instructions for a named Semiotic theme preset. Returns ThemeProvider examples, CSS custom propertie Read auditAccessibility Audit a Semiotic chart configuration against the Chartability (POUR-CAF) accessibility framework — Perceivable Read diagnoseConfig Diagnose a Semiotic chart configuration for common problems (empty data, bad dimensions, missing accessors, wr Read getSchema Return the prop schema for a Semiotic chart component. Pass { component: Read groundChart Build the agent-reader grounding payload for a Semiotic chart: the layered L1–L3 natural-language description, Read interrogateChart Conversational interrogation of a Semiotic chart. Extract a statistical summary and answer natural language qu Read proposeChartVariants Propose and score chart variants for a selected Semiotic component. Uses the capability registry plus heuristi Read repairChartConfig Validate that a chart component is a sensible choice for a dataset, and if not, propose alternatives that fit. Read suggestChart Lightweight heuristic chart recommender for a small data sample (1-5 rows) with capability filtering (push API Read suggestCharts Recommend Semiotic charts for a dataset using heuristic capability descriptors. Each chart declares which data Read suggestDashboard Generate a dashboard of complementary chart panels for a dataset — each panel answers a distinct analytical in Read suggestStreamCharts Recommend realtime/streaming Semiotic charts for a schema (not row data). Pass a schema describing field types Read suggestStretchCharts Recommend literacy-growth chart picks for a dataset given an AudienceProfile. Returns charts the data supports

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Semiotic

How do I prevent bulk modifications through Semiotic? +

The Semiotic server has 1 write tools including reportIssue. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Semiotic.

How many tools does the Semiotic MCP server expose? +

16 tools across 3 categories: Execute, Read, Write. 13 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Semiotic? +

Register the Semiotic MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Semiotic tool call.

Deterministic rules across all 16 Semiotic tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

16 Semiotic tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.