set_shared_context · Universal AI Chat MCP Server MCP

WHAT IT DOES

What set_shared_context does on Universal AI Chat MCP Server

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

WHY IT NEEDS A POLICY

Why set_shared_context needs a policy

The 'set_' prefix typically indicates a write/modification operation. In a multi-agent collaboration system, modifying shared context could affect all connected platforms and downstream agent behavior, but lacks the irreversibility of destructive operations or financial impact.

From the tool's definition Tool name 'set_shared_context' indicates modification of shared state. The description is empty, but contextual sibling tools (broadcast_message, get_shared_context, list_shared_context) and server purpose (shared vector memory between AI platforms) suggest…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_shared_context Rate-limited

set_shared_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": {
    "set_shared_context": {
      "limits": [
        {
          "counter": "set_shared_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 Universal AI Chat MCP Server, so you can run agents against it safely.

FAQ

Questions about set_shared_context

What does the set_shared_context tool do? +

set_shared_context. It is categorised as a Write tool in the Universal AI Chat 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 set_shared_context? +

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

What risk level is set_shared_context? +

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

Can I rate-limit set_shared_context? +

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

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

set_shared_context is provided by the Universal AI Chat MCP Server MCP server (marc-shade/universal-ai-chat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.