get_license_obligations
AI agents call get_license_obligations 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.
The tool appears to retrieve or query license obligation data as part of software composition analysis. No capability to modify, execute code, delete data, or move money is indicated. The naming pattern and server context (license detection, policy validation) suggest this retrieves pre-computed or database information without side effects.
From the tool's definition Tool name 'get_license_obligations' suggests retrieval of license information. Empty description limits direct evidence, but consistent with sibling tools like 'get_license_details' and 'generate_legal_notices' which are read operations on the SEMCL.ONE…
Attacks that exploit this kind of access
get_license_obligations. 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 get_license_obligations: 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.
get_license_obligations 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 get_license_obligations 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 get_license_obligations. 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.
get_license_obligations 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 →