list_compliance_logs
List compliance/bio-safety logs. Filterable by type (sterilization, needle_batch, ink_usage, sanitization) and practice. Inspector-ready.
This record as markdown: /tools/app-businys-mcp-server/list-compliance-logs.md
What list_compliance_logs does on Businys
AI agents call list_compliance_logs 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_compliance_logs is rated Low
This tool retrieves and filters existing compliance and bio-safety logs without creating, modifying, deleting, or executing any operations. It provides data visibility for audit and inspection purposes. The blast radius of misuse is minimal—an agent could retrieve logs it shouldn't access, but cannot alter records or trigger side effects. This is a straightforward Read operation with low severity.
From the tool's definition Tool name and description both indicate a retrieval function: 'List compliance/bio-safety logs' with filtering capabilities. Key verbs are 'List' and 'Filterable', which are read-only query operations.
Attacks that exploit this kind of access
The rule that runs list_compliance_logs 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_compliance_logs, this is the rule to start with:
list_compliance_logs 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_compliance_logs call is checked against it from then on.
Questions about list_compliance_logs
List compliance/bio-safety logs. Filterable by type (sterilization, needle_batch, ink_usage, sanitization) and practice. Inspector-ready. 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_compliance_logs: 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_compliance_logs 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_compliance_logs 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_compliance_logs. 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_compliance_logs 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