manage_project_context · Personal Knowledge Assistant MCP

WHAT IT DOES

What manage_project_context does on Personal Knowledge Assistant

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

WHY IT NEEDS A POLICY

Why manage_project_context needs a policy

This tool creates or modifies project-related data structures (contexts, tasks, deadlines) reversibly. It does not execute arbitrary code, delete data irreversibly, or move financial resources. While it could cause disruption if AI agents misuse prioritization logic, the effects are reversible through updates.

From the tool's definition Tool description states 'Manage project contexts, tasks, and deadlines' — 'manage' indicates creation and modification of data (tasks, deadlines, project contexts) rather than retrieval alone.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_project_context Rate-limited

manage_project_context 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": {
    "manage_project_context": {
      "limits": [
        {
          "counter": "manage_project_context_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 Personal Knowledge Assistant, so you can run agents against it safely.

FAQ

Questions about manage_project_context

What does the manage_project_context tool do? +

Manage project contexts, tasks, and deadlines with intelligent prioritization. It is categorised as a Write tool in the Personal Knowledge Assistant MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_project_context? +

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

What risk level is manage_project_context? +

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

Can I rate-limit manage_project_context? +

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

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

manage_project_context is provided by the Personal Knowledge Assistant MCP server (vitalune/nexus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.