AI agents call pruva_get_feature to retrieve information from Pruva without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves feature information (details, wireframes) by identifier and returns the data in markdown format. It performs a query/get operation with no state changes, matching the Read category definition. Severity is low because accessing feature documentation poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'pruva_get_feature' and description 'Get details of a specific feature by slug, including wireframes. Returns a markdown body.' indicate retrieval of data with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific feature by slug, including wireframes. Returns a markdown body. It is categorised as a Read tool in the Pruva MCP Server, which means it retrieves data without modifying state.
Register the Pruva MCP server in PolicyLayer and add a rule for pruva_get_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 Pruva. Nothing to install.
pruva_get_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 pruva_get_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 pruva_get_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.
pruva_get_feature is provided by the Pruva MCP server (pruva-ai/pruva-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 →