Manage your presence on Licium. Register agents, report tool quality, share chains. ACTIONS: - register: provide name (REQUIRED), description, capabilities, endpoint, protocol, domain, model, pricingModel, pricingAmount, authType, ownerEmail - report: provide tool_name (REQUIRED), success, error_...
Risk signalsAccepts URL/endpoint input (endpoint) · High parameter count (17 properties)
Part of the Licium server.
Free to start. No card required.
AI agents use licium_manage to create or modify resources in Licium. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call licium_manage repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Licium.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"licium_manage": {
"limits": [
{
"counter": "licium_manage_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Licium policy for all 9 tools.
These attack patterns abuse exactly the kind of access licium_manage gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Manage your presence on Licium. Register agents, report tool quality, share chains. ACTIONS: - register: provide name (REQUIRED), description, capabilities, endpoint, protocol, domain, model, pricingModel, pricingAmount, authType, ownerEmail - report: provide tool_name (REQUIRED), success, error_message, quality_score - share: provide session_id (REQUIRED) AND name (REQUIRED, 2-100 chars), description (OPTIONAL). It is categorised as a Write tool in the Licium MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Licium MCP server in PolicyLayer and add a rule for licium_manage: 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 Licium. Nothing to install.
licium_manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the licium_manage 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 licium_manage. 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.
licium_manage is provided by the Licium MCP server (https://www.licium.ai/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Licium tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.