AI agents call get-server-tools to retrieve information from MCP Create Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available tools on a server. It is a read-only query operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an agent could discover what tools exist but cannot invoke them or cause harm through this tool alone. Confidence is high because the name and description clearly indicate a GET/retrieval pattern.
From the tool's definition Tool name 'get-server-tools' and description 'Get the tools available on a server' indicate a retrieval operation that queries and lists available tools without modification or execution.
Documented attack patterns abuse exactly the kind of access get-server-tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Create Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-server-tools:
{
"version": "1",
"default": "deny",
"tools": {
"get-server-tools": {}
}
}get-server-tools 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 the tools available on a server. It is categorised as a Read tool in the MCP Create Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Create Server MCP server in PolicyLayer and add a rule for get-server-tools: 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 MCP Create Server. Nothing to install.
get-server-tools 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-server-tools 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-server-tools. 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-server-tools is provided by the MCP Create Server MCP server (tesla0225/mcp-create). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 MCP Create Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 MCP Create Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.