List jobs in the Hive. Filter by status/agent/since.
AI agents call hive.job_list to retrieve information from Mnemos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval tool that queries job records with optional filters. It does not create, modify, delete, or execute any operations—it only lists existing data. The blast radius of misuse is minimal; an agent could retrieve job information but cannot alter system state or trigger external actions.
From the tool's definition Tool name 'hive.job_list' and description 'List jobs in the Hive. Filter by status/agent/since.' indicate a query/retrieval operation with no side effects. The filtering parameters (status, agent, since) are all read-only criteria.
Documented attack patterns abuse exactly the kind of access hive.job_list 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_list:
{
"version": "1",
"default": "deny",
"tools": {
"hive.job_list": {}
}
}hive.job_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List jobs in the Hive. Filter by status/agent/since. It is categorised as a Read tool in the Mnemos MCP Server, which means it retrieves data without modifying state.
Register the Mnemos MCP server in PolicyLayer and add a rule for hive.job_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hive.job_list 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_list. 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_list 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.