Fast structural validation of formal spec without running solver. Auto-fixes: markdown fences, (check-sat)/(get-model), (set-logic). Checks: balanced parens, unfilled {{SLOT:}} markers, missing periods (Prolog). Returns cleaned spec + fixes applied + remaining errors.
AI agents use chiasmus_lint to create or update resources in Chiasmus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chiasmus environment.
An AI agent can call chiasmus_lint faster than any human can review — one bad instruction and it creates or modifies resources in Chiasmus by the hundred, each call as confident as the last.
Documented attack patterns abuse exactly the kind of access chiasmus_lint gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chiasmus, and nothing reaches the server without passing your rules. This is the rule we recommend for chiasmus_lint:
{
"version": "1",
"default": "deny",
"tools": {
"chiasmus_lint": {
"limits": [
{
"counter": "chiasmus_lint_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}chiasmus_lint stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fast structural validation of formal spec without running solver. Auto-fixes: markdown fences, (check-sat)/(get-model), (set-logic). Checks: balanced parens, unfilled {{SLOT:}} markers, missing periods (Prolog). Returns cleaned spec + fixes applied + remaining errors. It is categorised as a Write tool in the Chiasmus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Chiasmus MCP server in PolicyLayer and add a rule for chiasmus_lint: 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 Chiasmus. Nothing to install.
chiasmus_lint 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 chiasmus_lint 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 chiasmus_lint. 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.
chiasmus_lint is provided by the Chiasmus MCP server (yogthos/chiasmus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Chiasmus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Chiasmus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.