Submit work into the Hive Mind triage queue. Eligible agents self-claim.
AI agents use hive.job_create to create or update resources in Mnemos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mnemos environment.
The tool creates and submits new work items (jobs) into a queue, which is a write operation. It modifies state by adding records but does not execute arbitrary code, delete data irreversibly, or move funds. Severity is medium because job submissions could trigger downstream agent actions, but the tool itself only creates queue entries.
From the tool's definition Tool name 'hive.job_create' and description 'Submit work into the Hive Mind triage queue' indicate the tool creates new job records in a queue system. This is a reversible write operation that adds data to persistent storage.
Documented attack patterns abuse exactly the kind of access hive.job_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mnemos, and nothing reaches the server without passing your rules. This is the rule we recommend for hive.job_create:
{
"version": "1",
"default": "deny",
"tools": {
"hive.job_create": {
"limits": [
{
"counter": "hive.job_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}hive.job_create 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.
Submit work into the Hive Mind triage queue. Eligible agents self-claim. It is categorised as a Write tool in the Mnemos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mnemos MCP server in PolicyLayer and add a rule for hive.job_create: 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 Mnemos. Nothing to install.
hive.job_create 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 hive.job_create 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 hive.job_create. 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.
hive.job_create is provided by the Mnemos MCP server (ncz-os/mnemos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mnemos, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Mnemos tools catalogued and risk-classified — across an index of 43,000+ MCP servers.