Answer \
AI agents call check_pine_feature 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.
The tool appears designed to query or verify PineScript feature support by checking against engine capabilities. This is a read-only operation that retrieves information about supported features. Even with the truncated description, the name and context within a backtesting server suggest a lookup/inspection function rather than an action that modifies, executes, or deletes data.
From the tool's definition 'Answer' query operation with incomplete description suggests informational lookup; tool name 'check_pine_feature' indicates verification/inspection of Pine script features without modification or execution.
Attacks that exploit this kind of access
Answer \. 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 check_pine_feature: 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.
check_pine_feature 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 check_pine_feature 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 check_pine_feature. 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.
check_pine_feature 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 →