Medium Risk

set_summary

Set a brief summary (1-2 sentences) of what you are currently working on. This is visible to other Claude Code instances when they list peers.

How to control set_summary ↓

What set_summary does on Claude Peers

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

Medium Risk

Why set_summary needs a policy

This tool creates or modifies data (the work summary metadata) in a reversible manner. It does not execute code, delete data, or move money. The blast radius is minimal—a malicious agent could only set misleading summaries visible to other local instances, which is informational and easily corrected.

From the tool's definition Tool description states it 'Set[s] a brief summary' of current work that is 'visible to other Claude Code instances'. The verb 'set' indicates creation or modification of data (the summary).

Documented attack patterns abuse exactly the kind of access set_summary gives an agent:

How to control set_summary

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Peers, and nothing reaches the server without passing your rules. This is the rule we recommend for set_summary:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_summary": {
      "limits": [
        {
          "counter": "set_summary_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

set_summary 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.

  1. Create a free account and register Claude Peers — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about set_summary

What does the set_summary tool do? +

Set a brief summary (1-2 sentences) of what you are currently working on. This is visible to other Claude Code instances when they list peers. It is categorised as a Write tool in the Claude Peers 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_summary? +

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

What risk level is set_summary? +

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

Can I rate-limit set_summary? +

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

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

set_summary is provided by the Claude Peers MCP server (louislva/claude-peers-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Peers tool call.

Start from Claude Peers, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

4 Claude Peers tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.