Publish a short summary of what this Claude is working on.
AI agents use set_summary to create or update resources in Claude Mesh — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Mesh environment.
This tool creates or updates a summary document that describes current work status. It is reversible (the summary can be updated or cleared), has minimal blast radius, and affects only metadata/status information. It is Write rather than Execute because it merely records state rather than triggering external operations or code execution.
From the tool's definition Tool name 'set_summary' and description 'Publish a short summary' indicate creating or modifying status/state information. The word 'Publish' confirms a write action that creates or updates a summary artifact.
Documented attack patterns abuse exactly the kind of access set_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Mesh, and nothing reaches the server without passing your rules. This is the rule we recommend for set_summary:
{
"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.
Free to start. No card required.
Publish a short summary of what this Claude is working on. It is categorised as a Write tool in the Claude Mesh MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Mesh 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 Mesh. Nothing to install.
set_summary is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
set_summary is provided by the Claude Mesh MCP server (pouriamrt/claude-mesh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Mesh, 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 Mesh tools catalogued and risk-classified — across an index of 43,000+ MCP servers.