list_shared_context
AI agents call list_shared_context to retrieve information from Universal AI Chat MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's name strongly suggests it retrieves or enumerates shared context data. Despite the empty description reducing confidence moderately, the verb 'list' is consistently associated with Read category operations. The server's purpose (enabling communication and context sharing) implies this tool likely fetches stored or cached context rather than creating, deleting, or executing code.
From the tool's definition Tool name 'list_shared_context' uses the verb 'list', which typically indicates data retrieval without side effects.
Attacks that exploit this kind of access
list_shared_context. It is categorised as a Read tool in the Universal AI Chat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Universal AI Chat MCP Server MCP server in PolicyLayer and add a rule for list_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.
list_shared_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_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.
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 →