list_implementations
List AI implementation items \u2014 individual tasks within an engagement (model selection, data pipeline, prompt engineering, integration, testing, training). Filter by status or engagement.
This record as markdown: /tools/app-businys-mcp-server/list-implementations.md
What list_implementations does on Businys
AI agents call list_implementations to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_implementations is rated Low
This tool performs a query/list operation on existing AI implementation task records. It retrieves and filters data without side effects, making it a Read category tool with low severity. The blast radius of misuse is minimal—an AI agent could only over-retrieve or enumerate implementation details, but cannot modify, delete, or execute operations.
From the tool's definition Tool name 'list_implementations' and description 'List AI implementation items' indicates retrieval of data with filtering capability by status or engagement. No modification, deletion, or execution of operations mentioned.
Attacks that exploit this kind of access
The rule that runs list_implementations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_implementations, this is the rule to start with:
list_implementations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every list_implementations call is checked against it from then on.
Questions about list_implementations
List AI implementation items \u2014 individual tasks within an engagement (model selection, data pipeline, prompt engineering, integration, testing, training). Filter by status or engagement. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for list_implementations: 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 Businys. Nothing to install.
list_implementations 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 list_implementations 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 list_implementations. 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.
list_implementations is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue