lich_cong_tac
AI agents call lich_cong_tac to retrieve information from Mcp4xiaozhi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server's stated purpose (Vietnamese history events, news, fables) and sibling tools that are clearly informational/retrievals, this tool likely retrieves calendar or schedule data with no side effects. The empty description reduces confidence, but the naming pattern and server context suggest a Read operation. No evidence of data modification, deletion, code execution, or financial activity.
From the tool's definition Tool name 'lich_cong_tac' (Vietnamese for 'work schedule' or 'official calendar') and server context suggesting historical/news retrieval functions; description is empty, limiting certainty.
Attacks that exploit this kind of access
lich_cong_tac. It is categorised as a Read tool in the Mcp4xiaozhi MCP Server, which means it retrieves data without modifying state.
Register the Mcp4xiaozhi MCP server in PolicyLayer and add a rule for lich_cong_tac: 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 Mcp4xiaozhi. Nothing to install.
lich_cong_tac 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 lich_cong_tac 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 lich_cong_tac. 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.
lich_cong_tac is provided by the Mcp4xiaozhi MCP server (vdlaptrinh/mcp4xiaozhi). 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 →