factory_list_stubs

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dutydeck/factory-list-stubs.md

WHAT IT DOES

What factory_list_stubs does on DutyDeck

AI agents call factory_list_stubs to retrieve information from DutyDeck without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why factory_list_stubs is rated Low

Even though factory_list_stubs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs factory_list_stubs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For factory_list_stubs, this is the rule to start with:

factory_list_stubs Allowed

factory_list_stubs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "factory_list_stubs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DutyDeck, apply this rule, and every factory_list_stubs call is checked against it from then on.

FAQ

Questions about factory_list_stubs

What does the factory_list_stubs tool do? +

List the local capability stubs of this workspace: capabilityId, whether it is a placeholder, and the note. Read-only. Stubs stand in for capabilities the consuming project provides at runtime; they never enter the scene version or the delivered package. It is categorised as a Read tool in the DutyDeck MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on factory_list_stubs? +

Register the DutyDeck MCP server in PolicyLayer and add a rule for factory_list_stubs: 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 DutyDeck. Nothing to install.

What risk level is factory_list_stubs? +

factory_list_stubs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit factory_list_stubs? +

Yes. Add a rate_limit block to the factory_list_stubs 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.

How do I block factory_list_stubs completely? +

Set action: deny in the PolicyLayer policy for factory_list_stubs. 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.

What MCP server provides factory_list_stubs? +

factory_list_stubs is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on DutyDeck, and thousands of servers like it.

This server

All 247 DutyDeck tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →