Get the startup script attached to a specific Verda Cloud instance.
AI agents call get_instance_startup_script to retrieve information from Verda Cloud MCP Server 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 existing startup script data from a cloud instance. It performs no modifications, deletions, or executions—merely returning information about a configuration that already exists. While the startup script content could theoretically be sensitive, the tool itself only reads data.
From the tool's definition Tool description states 'Get the startup script attached to a specific Verda Cloud instance.' The verb 'Get' and the absence of any modification, deletion, or execution language indicate data retrieval without side effects.
Attacks that exploit this kind of access
Get the startup script attached to a specific Verda Cloud instance. It is categorised as a Read tool in the Verda Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Verda Cloud MCP Server MCP server in PolicyLayer and add a rule for get_instance_startup_script: 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 Verda Cloud MCP Server. Nothing to install.
get_instance_startup_script 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_instance_startup_script 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_instance_startup_script. 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_instance_startup_script is provided by the Verda Cloud MCP Server MCP server (sniper35/verda-cloud-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 →