AI agents call shared_contexts to retrieve information from Novyx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists data (shared contexts) available to the user without modifying, executing external code, or causing destructive effects. It is purely informational, fitting the Read category. Severity is low because listing accessible contexts has minimal blast radius—it reveals available data objects but does not expose sensitive content, execute code, or modify state.
From the tool's definition Tool name 'shared_contexts' and description 'List all shared contexts you have access to' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access shared_contexts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for shared_contexts:
{
"version": "1",
"default": "deny",
"tools": {
"shared_contexts": {}
}
} shared_contexts is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all shared contexts you have access to. It is categorised as a Read tool in the Novyx MCP Server, which means it retrieves data without modifying state.
Register the Novyx MCP server in PolicyLayer and add a rule for shared_contexts: 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 Novyx. Nothing to install.
shared_contexts 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 shared_contexts 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 shared_contexts. 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.
shared_contexts is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Novyx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
120 Novyx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.