matrix
Matrix Operations — Determinant, inverse, multiplication, and transpose for numeric matrices.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/matrix.md
What matrix does on Gateway
AI agents invoke matrix to trigger actions in Gateway. 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 |
|---|---|---|---|
a | array | Yes | 2D numeric matrix |
b | array | — | Second matrix (multiply) |
operation | string | — | Operation |
Parameters from the server's own tool schema.
Why matrix is rated High
This tool performs mathematical computations (determinant, inverse, multiplication, transpose) on numeric matrices. It executes calculations but has no side effects on data, files, or external systems. Classified as Execute rather than Read because it actively computes/transforms data rather than merely retrieving it.
From the tool's definition Matrix Operations — Determinant, inverse, multiplication, and transpose for numeric matrices.
Attacks that exploit this kind of access
The rule that runs matrix safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For matrix, this is the rule to start with:
matrix 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 Gateway, apply this rule, and every matrix call is checked against it from then on.
Questions about matrix
Matrix Operations — Determinant, inverse, multiplication, and transpose for numeric matrices. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
matrix accepts 3 parameters: a, b, operation. Required: a. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for matrix: 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 Gateway. Nothing to install.
matrix 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 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. 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 is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue