AI agents use accept_shared_context to create or update resources in Novyx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Novyx environment.
Accepting a shared context invitation modifies state by establishing a new shared context relationship. This is reversible in principle (context could later be revoked), making it a Write operation rather than Destructive. The blast radius is medium because accepting a shared context could expose an AI agent to external data or influence its memory/actions, but it does not directly delete data or execute code.
From the tool's definition Accept a shared context invitation
Documented attack patterns abuse exactly the kind of access accept_shared_context 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 accept_shared_context:
{
"version": "1",
"default": "deny",
"tools": {
"accept_shared_context": {
"limits": [
{
"counter": "accept_shared_context_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}accept_shared_context 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.
Accept a shared context invitation. It is categorised as a Write tool in the Novyx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Novyx MCP server in PolicyLayer and add a rule for accept_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 Novyx. Nothing to install.
accept_shared_context 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 accept_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 accept_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.
accept_shared_context 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.