matrix_decomp
Matrix decomposition and analysis: LU factorization, transpose, trace, or rank.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/matrix-decomp.md
What matrix_decomp does on UnClick
AI agents invoke matrix_decomp 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 |
|---|---|---|---|
matrix | array | Yes | 2D array of numbers (the matrix). |
operation | string | — | Operation: lu, transpose, trace, or rank (default lu). |
Parameters from the server's own tool schema.
Why matrix_decomp is rated High
This tool performs computational operations (LU factorization, transpose, trace, rank) on matrix inputs. These are mathematical computations that execute numerical algorithms rather than simply reading stored data or writing/modifying persistent state. No destructive, financial, or write side effects are implied.
From the tool's definition Matrix decomposition and analysis: LU factorization, transpose, trace, or rank
Attacks that exploit this kind of access
The rule that runs matrix_decomp 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 matrix_decomp, this is the rule to start with:
matrix_decomp 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 matrix_decomp call is checked against it from then on.
Questions about matrix_decomp
Matrix decomposition and analysis: LU factorization, transpose, trace, or rank. 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.
matrix_decomp accepts 2 parameters: matrix, operation. Required: matrix. 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 matrix_decomp: 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.
matrix_decomp 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 matrix_decomp 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 matrix_decomp. 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.
matrix_decomp 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