Start serving a model for inference on this node.
AI agents invoke serve_model to trigger actions in Tenzro Ledger MCP. 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.
This tool executes inference operations whose effects depend on which model is specified and what queries are run against it. While not immediately destructive or financial, it represents code execution that could consume computational resources, potentially be exploited to access sensitive model outputs, or be used for unauthorized processing.
From the tool's definition Tool name 'serve_model' with description 'Start serving a model for inference on this node' indicates execution of model inference operations on the node, which triggers external computational processes.
Attacks that exploit this kind of access
Start serving a model for inference on this node. It is categorised as a Execute tool in the Tenzro Ledger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for serve_model: 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 Tenzro Ledger MCP. Nothing to install.
serve_model 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 serve_model 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 serve_model. 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.
serve_model is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →