Query grammar productions captured from the spec's <emu-grammar> blocks. { nonterminal } returns every production for that non-terminal (exact match); { contains } filters by RHS / name substring; neither lists all non-terminals + their production counts. include_sdo folds in SDO-attached product...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Tc39 server.
Free to start. No card required.
AI agents call spec.grammar to retrieve information from Tc39 without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though spec.grammar only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"spec.grammar": {}
}
}See the full Tc39 policy for all 17 tools.
These attack patterns abuse exactly the kind of access spec.grammar gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Query grammar productions captured from the spec's <emu-grammar> blocks. { nonterminal } returns every production for that non-terminal (exact match); { contains } filters by RHS / name substring; neither lists all non-terminals + their production counts. include_sdo folds in SDO-attached productions (off by default).. It is categorised as a Read tool in the Tc39 MCP Server, which means it retrieves data without modifying state.
Register the Tc39 MCP server in PolicyLayer and add a rule for spec.grammar: 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 Tc39. Nothing to install.
spec.grammar 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 spec.grammar 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 spec.grammar. 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.
spec.grammar is provided by the Tc39 MCP server (tc39-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 Tc39 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.