get_workspace_settings

View your workspace configuration, enabled modules, rate limits, user count, and subscription details. Use this to understand what features are available. Enterprise only.

SERVERStarfield SOURCE@adrata/starfield-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/get-workspace-settings.md

WHAT IT DOES

What get_workspace_settings does on Starfield

AI agents call get_workspace_settings to retrieve information from Starfield without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_workspace_settings is rated Low

Even though get_workspace_settings only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_workspace_settings safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_workspace_settings, this is the rule to start with:

get_workspace_settings Allowed

get_workspace_settings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workspace_settings": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every get_workspace_settings call is checked against it from then on.

FAQ

Questions about get_workspace_settings

What does the get_workspace_settings tool do? +

View your workspace configuration, enabled modules, rate limits, user count, and subscription details. Use this to understand what features are available. Enterprise only. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workspace_settings? +

Register the Starfield MCP server in PolicyLayer and add a rule for get_workspace_settings: 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 Starfield. Nothing to install.

What risk level is get_workspace_settings? +

get_workspace_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workspace_settings? +

Yes. Add a rate_limit block to the get_workspace_settings 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.

How do I block get_workspace_settings completely? +

Set action: deny in the PolicyLayer policy for get_workspace_settings. 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.

What MCP server provides get_workspace_settings? +

get_workspace_settings is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Starfield, and thousands of servers like it.

This server

All 233 Starfield tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →