Create a tasking order for new satellite imagery capture with custom requirements
AI agents use skyfi_create_tasking_order to create or update resources in SkyFi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SkyFi MCP Server environment.
This tool creates a new tasking order, which is a write operation that modifies state in the SkyFi system by initiating a satellite imagery capture request. It is reversible (orders can presumably be cancelled), so it does not rise to Destructive.
From the tool's definition Tool name contains 'create' and description states 'Create a tasking order for new satellite imagery capture', indicating it creates a new record in SkyFi's tasking system.
Attacks that exploit this kind of access
Create a tasking order for new satellite imagery capture with custom requirements. It is categorised as a Write tool in the SkyFi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SkyFi MCP Server MCP server in PolicyLayer and add a rule for skyfi_create_tasking_order: 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 SkyFi MCP Server. Nothing to install.
skyfi_create_tasking_order 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 skyfi_create_tasking_order 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 skyfi_create_tasking_order. 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.
skyfi_create_tasking_order is provided by the SkyFi MCP Server MCP server (pskinnertech/skyfi-mcp-server). 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 →