AI agents call view_requirements_status to retrieve information from AI Develop Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about requirements documents. It performs a query/view operation on persistent storage without creating, modifying, deleting, or executing any operations. The action is read-only and presents no blast radius risk if misused by an AI agent—the worst outcome would be viewing status information that is already accessible.
From the tool's definition Tool name 'view_requirements_status' and description '查看当前需求文档的详细状态和内容' (View detailed status and content of current requirements document) indicate retrieval of existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access view_requirements_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AI Develop Assistant, and nothing reaches the server without passing your rules. This is the rule we recommend for view_requirements_status:
{
"version": "1",
"default": "deny",
"tools": {
"view_requirements_status": {}
}
}view_requirements_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
查看当前需求文档的详细状态和内容. It is categorised as a Read tool in the AI Develop Assistant MCP Server, which means it retrieves data without modifying state.
Register the AI Develop Assistant MCP server in PolicyLayer and add a rule for view_requirements_status: 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 AI Develop Assistant. Nothing to install.
view_requirements_status 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 view_requirements_status 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 view_requirements_status. 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.
view_requirements_status is provided by the AI Develop Assistant MCP server (jiemobasixiangcai/ai-develop-assistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AI Develop Assistant, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 AI Develop Assistant tools catalogued and risk-classified — across an index of 43,000+ MCP servers.