scan_directory
AI agents call scan_directory to retrieve information from Mcp Semclone without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Scanning a directory for composition analysis appears to be a read operation that queries data (file metadata, package information) without creating, executing external commands, deleting, or modifying data. The context of SEMCL.ONE toolchain for license detection and vulnerability assessment suggests this is information gathering.
From the tool's definition Tool name is 'scan_directory' with no description provided. Based on sibling tools on this server (analyze_commercial_risk, check_license_compatibility, check_package, download_and_scan_package, generate_sbom, etc.), this server performs software composition…
Attacks that exploit this kind of access
scan_directory. It is categorised as a Read tool in the Mcp Semclone MCP Server, which means it retrieves data without modifying state.
Register the Mcp Semclone MCP server in PolicyLayer and add a rule for scan_directory: 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 Mcp Semclone. Nothing to install.
scan_directory 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 scan_directory 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 scan_directory. 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.
scan_directory is provided by the Mcp Semclone MCP server (semclone/mcp-semclone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →