Submit a processed result to the Gravity Swarm. Takes the task_id and output from swarm_process. Signs the submission with your Nostr identity and sends it.
Part of the Gravity Swarm server.
Free to start. No card required.
AI agents use swarm_submit to create or modify resources in Gravity Swarm. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call swarm_submit repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Gravity Swarm.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"swarm_submit": {
"limits": [
{
"counter": "swarm_submit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Gravity Swarm policy for all 7 tools.
These attack patterns abuse exactly the kind of access swarm_submit gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Submit a processed result to the Gravity Swarm. Takes the task_id and output from swarm_process. Signs the submission with your Nostr identity and sends it.. It is categorised as a Write tool in the Gravity Swarm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gravity Swarm MCP server in PolicyLayer and add a rule for swarm_submit: 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 Gravity Swarm. Nothing to install.
swarm_submit 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 swarm_submit 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 swarm_submit. 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.
swarm_submit is provided by the Gravity Swarm MCP server (gravity-swarm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Gravity Swarm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.