worksection_activate_project · Worksection MCP Server MCP

WHAT IT DOES

What worksection_activate_project does on Worksection MCP Server

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

WHY IT NEEDS A POLICY

Why worksection_activate_project needs a policy

This tool creates a change to project state by unarchiving (reversing a previous destructive action), which is a reversible modification. While archive/unarchive operations can affect visibility and access, this is recoverable by re-archiving if needed. It is not Destructive (data is not deleted), not Execute (no code/script execution), and not Financial.

From the tool's definition Tool description states 'Activate (unarchive) a previously archived Worksection project' — this reverses an archival action and modifies project state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

worksection_activate_project Rate-limited

worksection_activate_project 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": {
    "worksection_activate_project": {
      "limits": [
        {
          "counter": "worksection_activate_project_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 Worksection MCP Server, so you can run agents against it safely.

FAQ

Questions about worksection_activate_project

What does the worksection_activate_project tool do? +

Activate (unarchive) a previously archived Worksection project. Args: - id_project (string, required): Project ID to activate Returns: Confirmation of activation. It is categorised as a Write tool in the Worksection MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on worksection_activate_project? +

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

What risk level is worksection_activate_project? +

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

Can I rate-limit worksection_activate_project? +

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

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

worksection_activate_project is provided by the Worksection MCP Server MCP server (novgorodskii/worksection-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.