depreciation
Depreciation Schedule Calculator — Straight-line or double-declining-balance schedule for an asset.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/depreciation.md
What depreciation does on Gateway
AI agents call depreciation to retrieve information from Gateway 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 |
|---|---|---|---|
cost | number | Yes | Asset cost in USD |
method | string | — | Depreciation method |
salvage_value | number | — | Salvage value at end of life, USD |
useful_life_years | integer | Yes | Useful life in years |
Parameters from the server's own tool schema.
Why depreciation is rated Low
This tool calculates and returns a depreciation schedule (a financial computation/report). It performs a read/query operation producing a schedule based on input parameters. It does not move money, modify data, execute code, or delete anything — it is a pure calculator returning informational output.
From the tool's definition Depreciation Schedule Calculator — Straight-line or double-declining-balance schedule for an asset
Attacks that exploit this kind of access
The rule that runs depreciation 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 depreciation, this is the rule to start with:
depreciation 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 Gateway, apply this rule, and every depreciation call is checked against it from then on.
Questions about depreciation
Depreciation Schedule Calculator — Straight-line or double-declining-balance schedule for an asset. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
depreciation accepts 4 parameters: cost, method, salvage_value, useful_life_years. Required: cost, useful_life_years. 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 depreciation: 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.
depreciation 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 depreciation 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 depreciation. 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.
depreciation 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.
This server
Across the catalogue