taylor_expand
Taylor series approximation for exp, sin, cos, ln(1+x), and atan(x).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/taylor-expand.md
What taylor_expand does on UnClick
AI agents call taylor_expand to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
x | number | Yes | Point to evaluate at. |
terms | number | — | Number of terms (default 10, max 50). |
function | string | Yes | Function: exp, sin, cos, ln1p, or atan. |
Parameters from the server's own tool schema.
Why taylor_expand is rated Low
Taylor series expansion is a mathematical operation that takes an input value and returns a computed approximation. It has no side effects on any data store, executes no external commands or code, and cannot delete or modify persistent state. It is fundamentally a read-only computational function, analogous to a mathematical library function.
From the tool's definition Tool description states it performs mathematical 'Taylor series approximation' for standard functions (exp, sin, cos, ln(1+x), atan). No parameters mentioned that would allow external data modification, deletion, or command execution.
Attacks that exploit this kind of access
The rule that runs taylor_expand 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 taylor_expand, this is the rule to start with:
taylor_expand is read-only, so it stays allowed. 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 taylor_expand call is checked against it from then on.
Questions about taylor_expand
Taylor series approximation for exp, sin, cos, ln(1+x), and atan(x). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
taylor_expand accepts 3 parameters: x, terms, function. Required: x, function. 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 taylor_expand: 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.
taylor_expand 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 taylor_expand 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 taylor_expand. 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.
taylor_expand 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.
This server
Across the catalogue