AI agents invoke latex_snippets_to_typst to trigger actions in Typst MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Based on the tool name, this appears to convert LaTeX snippets to Typst format, similar to the sibling tool 'latex_snippet_to_typst'. Conversion operations typically involve executing a transformation process. Since the description is empty, confidence is lowered. The sibling tool context suggests this is a batch version of latex_snippet_to_typst.
From the tool's definition Tool name: latex_snippets_to_typst; description is empty
Documented attack patterns abuse exactly the kind of access latex_snippets_to_typst gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Typst MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for latex_snippets_to_typst:
{
"version": "1",
"default": "deny",
"tools": {
"latex_snippets_to_typst": {
"limits": [
{
"counter": "latex_snippets_to_typst_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} latex_snippets_to_typst stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
latex_snippets_to_typst. It is categorised as a Execute tool in the Typst MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Typst MCP Server MCP server in PolicyLayer and add a rule for latex_snippets_to_typst: 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 Typst MCP Server. Nothing to install.
latex_snippets_to_typst is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the latex_snippets_to_typst 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 latex_snippets_to_typst. 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.
latex_snippets_to_typst is provided by the Typst MCP Server MCP server (johannesbrandenburger/typst-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Typst MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Typst MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.