prepare_spatial_handoff_manifest
Create a read-only handoff manifest for downstream VR/spatial tools from selected local assets and bounded nearby context.
This record as markdown: /tools/heznpc-airmcp/prepare-spatial-handoff-manifest.md
What prepare_spatial_handoff_manifest does on AirMCP
AI agents use prepare_spatial_handoff_manifest to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why prepare_spatial_handoff_manifest is rated Medium
This tool creates a new artifact (a handoff manifest) for use by other VR/spatial systems. While the resulting manifest is read-only for its consumers, the tool itself performs a write action by generating/preparing this data structure. This is reversible (the manifest can be deleted or regenerated), so it does not qualify as Destructive.
From the tool's definition Tool description explicitly states 'Create a...manifest' — the word 'Create' indicates data generation/modification.
Attacks that exploit this kind of access
The rule that runs prepare_spatial_handoff_manifest safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare_spatial_handoff_manifest, this is the rule to start with:
prepare_spatial_handoff_manifest 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 AirMCP, apply this rule, and every prepare_spatial_handoff_manifest call is checked against it from then on.
Questions about prepare_spatial_handoff_manifest
Create a read-only handoff manifest for downstream VR/spatial tools from selected local assets and bounded nearby context. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for prepare_spatial_handoff_manifest: 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 AirMCP. Nothing to install.
prepare_spatial_handoff_manifest 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 prepare_spatial_handoff_manifest 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 prepare_spatial_handoff_manifest. 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.
prepare_spatial_handoff_manifest is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue