context.create_packet
Create a compact component-local decision packet instead of sending the project.
This record as markdown: /tools/visionmcp/context.create-packet.md
What context.create_packet does on Visionmcp
AI agents use context.create_packet to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why context.create_packet is rated Medium
The tool creates a new data structure (decision packet) as a reversible operation. This is a Write action since it generates new artifacts within the system without permanent deletion or execution of arbitrary code.
From the tool's definition Tool description states 'Create a compact component-local decision packet', using the verb 'create' which indicates data creation/modification.
Attacks that exploit this kind of access
The rule that runs context.create_packet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For context.create_packet, this is the rule to start with:
context.create_packet 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every context.create_packet call is checked against it from then on.
Questions about context.create_packet
Create a compact component-local decision packet instead of sending the project. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for context.create_packet: 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 Visionmcp. Nothing to install.
context.create_packet 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 context.create_packet 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 context.create_packet. 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.
context.create_packet is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue