REQUIRED: Analyze a project BEFORE deploying. Returns technology stack, database needs, hosting compatibility, and warnings. You MUST call this tool first and show the analysis to the user before calling deploy_project. The user must confirm before deployment proceeds.
AI agents call analyze_project to retrieve information from Otoinstall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes project metadata to inform decision-making before deployment. It has no side effects, does not modify data, execute code, or trigger external operations. It functions as an informational/diagnostic tool, fitting the Read category. Severity is low because misuse only risks providing misleading analysis information, not actual system changes or resource consumption.
From the tool's definition Tool name 'analyze_project' and description states it 'Returns technology stack, database needs, hosting compatibility, and warnings.' The verb 'analyze' and 'returns' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
REQUIRED: Analyze a project BEFORE deploying. Returns technology stack, database needs, hosting compatibility, and warnings. You MUST call this tool first and show the analysis to the user before calling deploy_project. The user must confirm before deployment proceeds. It is categorised as a Read tool in the Otoinstall MCP Server, which means it retrieves data without modifying state.
Register the Otoinstall MCP server in PolicyLayer and add a rule for analyze_project: 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 Otoinstall. Nothing to install.
analyze_project 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 analyze_project 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 analyze_project. 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.
analyze_project is provided by the Otoinstall MCP server (otoinstall-mcp-server). 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 →