appflowy_set_publish_namespace · AppFlowy MCP: Risk & Policy

WHAT IT DOES

What appflowy_set_publish_namespace does on AppFlowy MCP

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

WHY IT NEEDS A POLICY

Why appflowy_set_publish_namespace needs a policy

This tool modifies workspace metadata (the publish namespace) but does not delete data or execute arbitrary code. The change is reversible—the namespace can be renamed again to a previous value. While this could affect workspace visibility/sharing if the namespace is used for public publishing, it remains a configuration write operation rather than destructive or executable.

From the tool's definition Tool name 'appflowy_set_publish_namespace' and description 'Rename the workspace publish namespace' indicate modification of workspace configuration settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

appflowy_set_publish_namespace Rate-limited

appflowy_set_publish_namespace 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": {
    "appflowy_set_publish_namespace": {
      "limits": [
        {
          "counter": "appflowy_set_publish_namespace_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 AppFlowy MCP, so you can run agents against it safely.

FAQ

Questions about appflowy_set_publish_namespace

What does the appflowy_set_publish_namespace tool do? +

Rename the workspace publish namespace. It is categorised as a Write tool in the AppFlowy 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 appflowy_set_publish_namespace? +

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

What risk level is appflowy_set_publish_namespace? +

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

Can I rate-limit appflowy_set_publish_namespace? +

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

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

appflowy_set_publish_namespace is provided by the AppFlowy MCP server (weironz/appflowy_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.