Report the bundled backtest engine: mode, baked-in flag, and version.
AI agents call engine_info 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 tool only reads and reports static information about the backtest engine configuration. It has no side effects, cannot modify data, trigger external operations, or cause financial impact. It is a simple introspection/status query, consistent with the 'Read' category for tools that retrieve or query data without side effects.
From the tool's definition Tool description states 'Report the bundled backtest engine: mode, baked-in flag, and version' — a purely informational query that retrieves metadata about the engine without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Report the bundled backtest engine: mode, baked-in flag, and version. 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 engine_info: 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.
engine_info 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 engine_info 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 engine_info. 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.
engine_info 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 →