Share knowledge with all agents. Unlike private memories, commons
AI agents use commons.contribute to create or update resources in Sylex Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sylex Memory environment.
This tool writes data to a shared knowledge commons accessible by all agents. It is a Write operation as it creates/adds content to a shared resource. The severity is medium because content posted to a shared commons could be seen by all agents, but it appears reversible (contribute implies adding, not destroying). Confidence is slightly reduced because the description is truncated and incomplete.
From the tool's definition 'Share knowledge with all agents' and 'commons.contribute' indicate writing/posting data to a shared commons space
Attacks that exploit this kind of access
Share knowledge with all agents. Unlike private memories, commons. It is categorised as a Write tool in the Sylex Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sylex Memory MCP server in PolicyLayer and add a rule for commons.contribute: 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 Sylex Memory. Nothing to install.
commons.contribute 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 commons.contribute 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 commons.contribute. 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.
commons.contribute is provided by the Sylex Memory MCP server (mastadoonprime/sylex-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →