get_sheet_names
A read tool on the MCP Framework Personal MCP server.
This record as markdown: /tools/inggerman-mcps/get-sheet-names.md
What get_sheet_names does on MCP Framework Personal
AI agents call get_sheet_names to retrieve information from MCP Framework Personal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_sheet_names is rated Low
The tool appears to query and return metadata about available sheets/tabs in a tabular data source. This is a non-mutating read operation with no side effects. Low severity because retrieving sheet names poses minimal risk even if misused by an agent. The empty description reduces confidence slightly, but the naming pattern and peer tools strongly indicate a read-only query function.
From the tool's definition Tool name 'get_sheet_names' indicates retrieval of sheet names from a data source. No description provided, but naming convention and context among sibling tools (get_file_summary, get_column_stats, get_frontmatter) which are all read-only queries suggests…
Attacks that exploit this kind of access
The rule that runs get_sheet_names safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_sheet_names, this is the rule to start with:
get_sheet_names 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 MCP Framework Personal, apply this rule, and every get_sheet_names call is checked against it from then on.
Questions about get_sheet_names
get_sheet_names is a read tool on the MCP Framework Personal MCP server. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for get_sheet_names: 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 Framework Personal. Nothing to install.
get_sheet_names 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_sheet_names 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_sheet_names. 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_sheet_names is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue