ntt
Multiply two polynomials using Number Theoretic Transform (mod 998244353).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/ntt.md
What ntt does on UnClick
AI agents invoke ntt to trigger actions in UnClick. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
poly_a | array | Yes | First polynomial coefficients |
poly_b | array | Yes | Second polynomial coefficients |
Parameters from the server's own tool schema.
Why ntt is rated High
This tool executes a numerical algorithm (NTT) to compute a result. It has no side effects on data, money, or files — it's a pure computation. Execute is the most appropriate category since it runs a transform algorithm, though the blast radius is very low as it cannot affect external systems.
From the tool's definition "Multiply two polynomials using Number Theoretic Transform (mod 998244353)" — performs a mathematical computation/algorithm execution
Attacks that exploit this kind of access
The rule that runs ntt safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ntt, this is the rule to start with:
ntt 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every ntt call is checked against it from then on.
Questions about ntt
Multiply two polynomials using Number Theoretic Transform (mod 998244353). It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
ntt accepts 2 parameters: poly_a, poly_b. Required: poly_a, poly_b. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for ntt: 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 UnClick. Nothing to install.
ntt 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 ntt 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 ntt. 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.
ntt is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue