Returns the full catalog of engine knobs accepted by backtest_pine /
AI agents call list_engine_params to retrieve information from PineForge-Codegen without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a purely informational query tool that enumerates configuration options. It has no side effects, does not execute code, does not modify state, and poses minimal risk if misused by an AI agent (worst case: agent learns what parameters are available, which is not harmful). Categorized as Read.
From the tool's definition Tool returns/retrieves a catalog of parameters—'Returns the full catalog of engine knobs accepted by backtest_pine'. No modification, deletion, execution, or financial activity occurs.
Attacks that exploit this kind of access
Returns the full catalog of engine knobs accepted by backtest_pine /. It is categorised as a Read tool in the PineForge-Codegen MCP Server, which means it retrieves data without modifying state.
Register the PineForge-Codegen MCP server in PolicyLayer and add a rule for list_engine_params: 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 PineForge-Codegen. Nothing to install.
list_engine_params 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 list_engine_params 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 list_engine_params. 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.
list_engine_params is provided by the PineForge-Codegen MCP server (oci:ghcr.io/pineforge-4pass/pineforge-codegen-mcp:v0.9.2). 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 →