Get full workspace metadata including internal IDs, organization binding, creator userId, and creation/update timestamps. Provides deeper detail than list_workspaces. Useful for debugging or workspace administration.
AI agents call get_workspace_detail to retrieve information from Fusebase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries workspace metadata—a read-only operation with no side effects. However, the severity is elevated to 'medium' rather than 'low' because the metadata returned includes sensitive information (internal IDs, creator userIds, organization binding) that could be leveraged for reconnaissance or privilege escalation if an agent misuses it to map organizational structure or identify high-value…
From the tool's definition Tool name 'get_workspace_detail' and description stating it 'Get[s] full workspace metadata including internal IDs, organization binding, creator userId, and creation/update timestamps.' This is a retrieval operation with no modifications.
Attacks that exploit this kind of access
Get full workspace metadata including internal IDs, organization binding, creator userId, and creation/update timestamps. Provides deeper detail than list_workspaces. Useful for debugging or workspace administration. It is categorised as a Read tool in the Fusebase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Fusebase MCP Server MCP server in PolicyLayer and add a rule for get_workspace_detail: 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 Fusebase MCP Server. Nothing to install.
get_workspace_detail 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_workspace_detail 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_workspace_detail. 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_workspace_detail is provided by the Fusebase MCP Server MCP server (ryan-haver/fusebase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →