AI agents call list_feature_views to retrieve information from Tecton without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data from a feature store without causing any side effects. It is a passive read operation that enumerates existing feature views. The blast radius of misuse is minimal—an attacker would only gain visibility into feature store configuration but cannot modify, delete, or execute operations. Classified as Read with low severity.
From the tool's definition Tool name contains 'list' and description states 'List all feature views in the currently connected tecton cluster' with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List all feature views in the currently connected tecton cluster. It is categorised as a Read tool in the Tecton MCP Server, which means it retrieves data without modifying state.
Register the Tecton MCP server in PolicyLayer and add a rule for list_feature_views: 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 Tecton. Nothing to install.
list_feature_views 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_feature_views 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_feature_views. 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_feature_views is provided by the Tecton MCP server (slavovthinks/tecton-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 →