get_teamspace
Get details for a Huly document teamspace including document count. Finds by name or ID, including archived teamspaces.
This record as markdown: /tools/dugynoo-huly-mcp/get-teamspace.md
What get_teamspace does on Huly
AI agents call get_teamspace to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_teamspace is rated Low
This tool only retrieves/queries data about a teamspace with no side effects. It is a pure read operation with low blast radius if misused.
From the tool's definition 'Get details for a Huly document teamspace' — retrieves information about a teamspace including document count, finds by name or ID
Attacks that exploit this kind of access
The rule that runs get_teamspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_teamspace, this is the rule to start with:
get_teamspace 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 Huly, apply this rule, and every get_teamspace call is checked against it from then on.
Questions about get_teamspace
Get details for a Huly document teamspace including document count. Finds by name or ID, including archived teamspaces. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for get_teamspace: 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 Huly. Nothing to install.
get_teamspace 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_teamspace 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_teamspace. 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_teamspace is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue