get_current_workspace

Get details about the current workspace including subscription tier, member count, link count, project count, and settings. Returns the workspace bound to the active API key.

Server LinkForty MCP Server linkforty/mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_current_workspace does on LinkForty MCP Server

AI agents call get_current_workspace to retrieve information from LinkForty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_current_workspace needs a policy

This is a query operation that retrieves metadata about the current workspace. It has no side effects—it only reads and returns configuration and status information bound to the active API key. The returned data (counts, settings, subscription info) are informational only.

From the tool's definition Tool retrieves workspace details including subscription tier, member count, link count, project count, and settings. Uses 'Get' prefix and returns read-only information without modifying data.

Questions about get_current_workspace

What does the get_current_workspace tool do? +

Get details about the current workspace including subscription tier, member count, link count, project count, and settings. Returns the workspace bound to the active API key. It is categorised as a Read tool in the LinkForty MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_workspace? +

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

What risk level is get_current_workspace? +

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

Can I rate-limit get_current_workspace? +

Yes. Add a rate_limit block to the get_current_workspace 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_current_workspace completely? +

Set action: deny in the PolicyLayer policy for get_current_workspace. 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_current_workspace? +

get_current_workspace is provided by the LinkForty MCP Server MCP server (linkforty/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.