get_method_signature
Get the formal signature(s) of a method on a type — parameter names, types, defaults, return type, all overloads. Use before invoking an API you
This record as markdown: /tools/sbox/get-method-signature.md
What get_method_signature does on Sbox
AI agents call get_method_signature to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_method_signature is rated Low
This tool performs introspection/metadata retrieval on method signatures. It has no side effects, does not execute code, and does not modify any game state or data. It is purely informational, used to gather information before making other API calls. This is a classic Read operation.
From the tool's definition Tool description states 'Get the formal signature(s) of a method on a type' — this is a retrieval operation that queries metadata about methods without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_method_signature safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_method_signature, this is the rule to start with:
get_method_signature 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 Sbox, apply this rule, and every get_method_signature call is checked against it from then on.
Questions about get_method_signature
Get the formal signature(s) of a method on a type — parameter names, types, defaults, return type, all overloads. Use before invoking an API you. It is categorised as a Read tool in the Sbox MCP Server, which means it retrieves data without modifying state.
Register the Sbox MCP server in PolicyLayer and add a rule for get_method_signature: 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 Sbox. Nothing to install.
get_method_signature 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_method_signature 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_method_signature. 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_method_signature is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sbox, and thousands of servers like it.
This server
Across the catalogue