update_user_context · PlugLayer MCP Server MCP

WHAT IT DOES

What update_user_context does on PlugLayer MCP Server

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

WHY IT NEEDS A POLICY

Why update_user_context needs a policy

This tool modifies user context data that persists across sessions, affecting preferences and deployment mappings. While the effects are reversible (another update could change or clear the context), misuse could corrupt user preferences, interfere with automated deployment workflows, or cause subsequent operations to target wrong projects/apps.

From the tool's definition The tool description states 'Update the caller's stored PlugLayer user context memory,' which indicates creation or modification of data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_user_context Rate-limited

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

FAQ

Questions about update_user_context

What does the update_user_context tool do? +

Update the caller's stored PlugLayer user context memory. Use this carefully for durable preferences, project/app mappings, prior decisions, and user-specific deployment habits. It is categorised as a Write tool in the PlugLayer 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 update_user_context? +

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

What risk level is update_user_context? +

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

Can I rate-limit update_user_context? +

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

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

update_user_context is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.