collab_session_close

Close session; optionally package/publish market product.

SERVERDual Registry SOURCEhttps://www.dualregistry.dev/api/protocol

Medium RISK CLASS

Category Write

Parameters 81 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-dualregistry-registry/collab-session-close.md

WHAT IT DOES

What collab_session_close does on Dual Registry

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

Parameter	Type	Required
`title`	string	—
`publish`	boolean	—
`agent_name`	string	—
`listing_id`	string	—
`session_id`	string	Yes
`price_cents`	number	—
`access_token`	string	—
`payment_proof`	boolean	—

Parameters from the server's own tool schema.

RISK

Why collab_session_close is rated Medium

An AI agent can call collab_session_close faster than any human can review: one bad instruction and it creates or modifies resources in Dual Registry by the hundred, each call as confident as the last.

Risk signalsHandles credentials or secrets (access_token)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs collab_session_close safely

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

collab_session_close Rate-limited

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

FAQ

Questions about collab_session_close

What does the collab_session_close tool do? +

Close session; optionally package/publish market product. It is categorised as a Write tool in the Dual Registry MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does collab_session_close accept? +

collab_session_close accepts 8 parameters: title, publish, agent_name, listing_id, session_id, price_cents, access_token, payment_proof. Required: session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on collab_session_close? +

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

What risk level is collab_session_close? +

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

Can I rate-limit collab_session_close? +

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

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

collab_session_close is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dual Registry, and thousands of servers like it.

This server

All 64 Dual Registry tools →

Across the catalogue

The MCP Attack Database →

Guides

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