This record as markdown: /tools/frontmcp/serverless-info.md
What serverless-info does on Frontmcp
AI agents call serverless-info to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why serverless-info is rated Low
This tool retrieves and returns information about the deployment environment. It is a simple data retrieval operation with no capability to modify state, execute code, delete data, or move funds. The lowest-impact classification (Read) is appropriate.
From the tool's definition Tool name 'serverless-info' and description 'Returns deployment environment information' indicate a read-only retrieval operation with no side effects. Querying or fetching environment metadata does not modify, execute, or delete data.
Attacks that exploit this kind of access
The rule that runs serverless-info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For serverless-info, this is the rule to start with:
serverless-info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every serverless-info call is checked against it from then on.
Questions about serverless-info
Returns deployment environment information. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for serverless-info: 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 Frontmcp. Nothing to install.
serverless-info 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 serverless-info 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 serverless-info. 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.
serverless-info is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue