Retrieve a feature specification from Rampify. Use this when starting work on a feature to understand what to build, which files to touch, and what the acceptance criteria are. Two lookup modes: - spec_id: fetch a specific spec with full criteria and tasks (use this when you know the ID) - search...
AI agents call get_feature_spec to retrieve information from Rampify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval operations only—fetching existing feature specifications from the Rampify system. No write, modification, deletion, code execution, or financial operations are possible. The dual-mode operation (spec lookup or search) both result in read-only access to specification data. This is a standard information retrieval operation with minimal risk if misused by an AI agent.
From the tool's definition Tool retrieves feature specifications via 'spec_id' lookup or 'search' across titles and descriptions. Described as 'Retrieve' which indicates data fetching with no modification capability. Returns specifications and acceptance criteria.
Attacks that exploit this kind of access
Retrieve a feature specification from Rampify. Use this when starting work on a feature to understand what to build, which files to touch, and what the acceptance criteria are. Two lookup modes: - spec_id: fetch a specific spec with full criteria and tasks (use this when you know the ID) - search: keyword search across titles and descriptions (returns a list; follow up with spec_id for full details). It is categorised as a Read tool in the Rampify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rampify MCP Server MCP server in PolicyLayer and add a rule for get_feature_spec: 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 Rampify MCP Server. Nothing to install.
get_feature_spec 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 get_feature_spec 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 get_feature_spec. 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.
get_feature_spec is provided by the Rampify MCP Server MCP server (rampify-dev/rampify-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 →