set_page_visibility · Hubnote MCP: Risk & Policy

WHAT IT DOES

What set_page_visibility does on Hubnote Mcp

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

WHY IT NEEDS A POLICY

Why set_page_visibility needs a policy

Toggling visibility is a reversible modification of page metadata/configuration that controls who can access the page. This is a Write operation (not Destructive, as visibility changes can be undone). Medium severity because misconfigured visibility could expose sensitive workspace data to unintended audiences, but the blast radius depends on workspace contents and the specific visibility settings applied.

From the tool's definition Tool name 'set_page_visibility' indicates modification of page access control settings. Description is incomplete ('Toggle a page between') but the function clearly modifies page state rather than merely retrieving or deleting it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_page_visibility Rate-limited

set_page_visibility 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": {
    "set_page_visibility": {
      "limits": [
        {
          "counter": "set_page_visibility_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Hubnote Mcp, so you can run agents against it safely.

FAQ

Questions about set_page_visibility

What does the set_page_visibility tool do? +

Toggle a page between. It is categorised as a Write tool in the Hubnote Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_page_visibility? +

Register the Hubnote MCP server in PolicyLayer and add a rule for set_page_visibility: 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 Hubnote Mcp. Nothing to install.

What risk level is set_page_visibility? +

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

Can I rate-limit set_page_visibility? +

Yes. Add a rate_limit block to the set_page_visibility 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 set_page_visibility completely? +

Set action: deny in the PolicyLayer policy for set_page_visibility. 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 set_page_visibility? +

set_page_visibility is provided by the Hubnote MCP server (wlzerd/hubnote-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.