setKgProjectVisibility

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/setkgprojectvisibility.md

WHAT IT DOES

What setKgProjectVisibility does on Stable Baseline

AI agents use setKgProjectVisibility to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.

Parameter	Type	Required	Description
`mode`	string	Yes
`project_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why setKgProjectVisibility is rated Medium

This tool creates or modifies access control settings for Knowledge Graph data visibility within a project. While it affects who can read data, the core action is modifying project configuration state—a reversible write operation. It is not Destructive (visibility can be changed back), not Execute (no code/commands run), not Financial (no monetary transfers), and not Read (it actively changes state).

From the tool's definition Tool description states it 'Set[s] the KG visibility mode for a project' and 'Controls WHO can see the project's KG rows.' This modifies project configuration (visibility settings) reversibly via the 'strict', 'permissive', or 'open' modes.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs setKgProjectVisibility safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For setKgProjectVisibility, this is the rule to start with:

setKgProjectVisibility Rate-limited

setKgProjectVisibility stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "setKgProjectVisibility": {
      "limits": [
        {
          "counter": "setkgprojectvisibility_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stable Baseline, apply this rule, and every setKgProjectVisibility call is checked against it from then on.

FAQ

Questions about setKgProjectVisibility

What does the setKgProjectVisibility tool do? +

Set the KG visibility mode for a project: 'strict' (multi-source rows hidden unless user can read every source), 'permissive' (one source suffices), or 'open' (any org member). Controls WHO can see the project's KG rows. Requires can_manage_kg + project write. Rate limit 30/min. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does setKgProjectVisibility accept? +

setKgProjectVisibility accepts 2 parameters: mode, project_id. Required: mode, project_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on setKgProjectVisibility? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for setKgProjectVisibility: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Stable Baseline. Nothing to install.

What risk level is setKgProjectVisibility? +

setKgProjectVisibility is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit setKgProjectVisibility? +

Yes. Add a rate_limit block to the setKgProjectVisibility rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block setKgProjectVisibility completely? +

Set action: deny in the PolicyLayer policy for setKgProjectVisibility. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides setKgProjectVisibility? +

setKgProjectVisibility is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 196 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →