Get detailed information about a specific script
AI agents call script_get to retrieve information from ScriptFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The script_get tool retrieves metadata or content about an existing script without altering it, executing it, or deleting it. This is a straightforward read operation with minimal blast radius if misused—an AI agent could only access information about scripts, not execute them or modify system state.
From the tool's definition Tool name 'script_get' and description 'Get detailed information about a specific script' indicate a retrieval operation with no modification or execution.
Documented attack patterns abuse exactly the kind of access script_get gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScriptFlow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for script_get:
{
"version": "1",
"default": "deny",
"tools": {
"script_get": {}
}
}script_get 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.
Get detailed information about a specific script. It is categorised as a Read tool in the ScriptFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ScriptFlow MCP Server MCP server in PolicyLayer and add a rule for script_get: 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 ScriptFlow MCP Server. Nothing to install.
script_get 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 script_get 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 script_get. 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.
script_get is provided by the ScriptFlow MCP Server MCP server (yanmxa/scriptflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScriptFlow MCP Server, 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.
6 ScriptFlow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.