Stable Baseline

184 tools. 115 can modify or destroy data without limits.

28 destructive tools with no built-in limits. Policy required.

Last updated:

115 can modify or destroy data
69 read-only
184 tools total

115 Stable Baseline tools can modify or destroy data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE STABLE BASELINE →

Free to start. No card required.

Read (69) Write / Execute (87) Destructive / Financial (28)
35,752 tokens of tool definitions, loaded on every request
18% of a 200k context window
3,363 heaviest tool: addWhiteboardElements

Destructive tools (acceptTaskDependencyReview, cancelAllKgInScope, cancelInvitation) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (addImprovementActivity, addImprovementEvidence, addPlanActivity) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (designWhiteboard, duplicateWhiteboardElements, previewTaskDependencyCascade) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

Deny destructive operations
{
  "acceptTaskDependencyReview": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

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

Prevents bulk unintended modifications from agents caught in loops.

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

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

Get this policy live on your own Stable Baseline server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY STABLE BASELINE →
WRITE 78 tools
Write addImprovementActivity Write addImprovementEvidence Write addPlanActivity Write addTeamMember Write addWhiteboardElements Write addWorkspaceMember Write applyKgScopeChange Write applySubscriptionChange Write applyTaskDependencyCascade Write createDocument Write createDocumentFromUpload Write createDocumentIngestSession Write createFolder Write createImageUploadSession Write createImprovement Write createImprovementCategory Write createOrganisation Write createPlan Write createPlanPhase Write createProject Write createTask Write createTaskDependency Write createTeam Write createVegaDataUploadSession Write createWhiteboard Write createWorkspace Write editDocument Write grantTeamWorkspaceAccess Write insertDiagramInDocument Write insertImageInDocument Write insertWhiteboardDiagram Write insertWhiteboardImage Write inviteMember Write kg_backlinks Write kg_evaluate_retrieval Write kg_related_documents Write kg_suggest_sample_questions Write previewKgRebuild Write previewKgScopeChange Write previewSubscriptionChange Write rebuildPlatformCatalogEmbeddings Write reorderDocuments Write reorderFolders Write reorderImprovementCategories Write reorderPlanPhases Write setKgDocumentScope Write setKgFolderScope Write setKgProjectVisibility Write setKgWorkspaceScope Write setMemberActive Write setPlanItemParent Write setResourcePermissionOverride Write updateBillingEmail Write updateDiagramInDocument Write updateFolder Write updateImageInDocument Write updateImprovement Write updateImprovementCategory Write updateImprovementComment Write updateMemberRole Write updateOrganisation Write updateOrgFeatureFlags Write updateOrgSettings Write updatePlan Write updatePlanComment Write updatePlanPhase Write updateProfile Write updateProject Write updateResourcePermission Write updateTask Write updateTaskDependency Write updateTeam Write updateTeamWorkspaceAccess Write updateUserPreferences Write updateWhiteboardScene Write updateWorkspace Write updateWorkspaceMember Write upsertResourcePermission
READ 69 tools
Read dataToTable Read findAndReplaceTextInDocument Read getCdmdLanguageGuide Read getCreditBalance Read getCreditPackages Read getCurrentPlanEntitlements Read getCurrentUser Read getCustomerPortalLink Read getDiagramImage Read getDiagramInDocument Read getDiagramTypeGuide Read getDocument Read getDocumentIngestJob Read getEffectivePermission Read getFolderHierarchy Read getImageInDocument Read getImprovement Read getKgScopeTree Read getMember Read getOrganisation Read getOrgSettings Read getPlan Read getPlanHierarchy Read getPlanPhase Read getPriceForTier Read getProject Read getProjectHierarchy Read getSubscription Read getTask Read getTeam Read getUserPreferences Read getWhiteboard Read getWhiteboardGuide Read getWhiteboardImage Read getWorkspace Read kg_get_entity Read kg_get_wiki_page Read kg_list_communities Read kg_scope_status Read kg_search Read listArchitectureIcons Read listAssignablePrincipals Read listCreditPurchases Read listDiagramTypes Read listDocuments Read listDocumentVersions Read listFolders Read listImprovementCategories Read listImprovements Read listInvitations Read listInvoices Read listMembers Read listOrganisations Read listPaymentMethods Read listPlanPhases Read listPlans Read listProjects Read listResourcePermissions Read listTaskDependencies Read listTasks Read listTeams Read listWhiteboards Read listWhiteboardStencils Read listWorkspaces Read pollSignupStatus Read searchImprovements Read searchInfographicTemplates Read searchTools Read traceImage
Can an AI agent delete data through the Stable Baseline MCP server? +

Yes. The Stable Baseline server exposes 28 destructive tools including acceptTaskDependencyReview, cancelAllKgInScope, cancelInvitation. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Stable Baseline? +

The Stable Baseline server has 78 write tools including addImprovementActivity, addImprovementEvidence, addPlanActivity. 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 Stable Baseline.

How many tools does the Stable Baseline MCP server expose? +

184 tools across 4 categories: Destructive, Execute, Read, Write. 69 are read-only. 115 can modify, create, or delete data.

How do I enforce a policy on Stable Baseline? +

Register the Stable Baseline 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.

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every Stable Baseline tool call.

Deterministic rules across all 184 Stable Baseline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.