wall_mcp_publish

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Medium RISK CLASS

Category Write

Parameters 10 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/wall-mcp-publish.md

WHAT IT DOES

What wall_mcp_publish does on Rokha

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

Parameter	Type	Required	Description
`mcp_url`	string	—	your MCP server's streamable-http endpoint (https://…/mcp) — optional if your seat already carries one

Parameters from the server's own tool schema.

RISK

Why wall_mcp_publish is rated Medium

Creates or updates a public registry listing by probing and publishing an MCP server endpoint.

From the tool's definition publishes your registry listing...link your own remote MCP server

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs wall_mcp_publish safely

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

wall_mcp_publish Rate-limited

wall_mcp_publish 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": {
    "wall_mcp_publish": {
      "limits": [
        {
          "counter": "wall_mcp_publish_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 Rokha, apply this rule, and every wall_mcp_publish call is checked against it from then on.

FAQ

Questions about wall_mcp_publish

What does the wall_mcp_publish tool do? +

A live-seat perk on The Network (rokha.ai/network): link your own remote MCP server and Rokha publishes your registry listing from it — you as the source, credited to your seat. We probe the endpoint for real (initialize + tools/list, SSRF-gated); a dead door or empty roster refuses with the evidence. The listing is built from your live seat card (title, pitch, blurb, creative-as-logo) plus the probed tool roster — nothing hand-written, so it can't drift from what you actually serve. Idempotent per slug (<your-title>-seat-mcp); re-running refreshes the roster. It carries NO official badge — that mark means superadmin-verified vendor provenance and is never sold; your listing is bound to your seat by proven ownership instead. Once live, the board's ◆ On the Registry link and agent recalls light up on their own, and users filter the registry on your brand tag. Optionally pass mcp_url to set/replace your seat's MCP door in the same call (it also lives at PATCH /api/pages/me/seat). Seat sales are retired (2026-10-01) — this door serves the Founding Members' seats; new members join the Rokha Network at rokha.ai/network. Requires Authorization: Bearer <JWT> from the seat's claimed owner (or the account whose page X handle matches the seat's sponsor). It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does wall_mcp_publish accept? +

wall_mcp_publish accepts 1 parameter: mcp_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on wall_mcp_publish? +

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

What risk level is wall_mcp_publish? +

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

Can I rate-limit wall_mcp_publish? +

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

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

wall_mcp_publish is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

The MCP Attack Database →

Guides

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