This record as markdown: /tools/ruflo/teammate-get-status.md
What teammate_get_status does on Ruflo
AI agents call teammate_get_status to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why teammate_get_status is rated Low
This tool retrieves status information about teams and teammates. The verb 'get' and the absence of any language suggesting modification, deletion, or code execution clearly categorize this as a Read operation. The severity is low because status queries have no side effects and minimal blast radius—an AI agent cannot cause harm by checking status information.
From the tool's definition Tool name 'teammate_get_status' and description 'Get team and teammate status' indicate a retrieval operation that queries state information without modification or execution.
Attacks that exploit this kind of access
The rule that runs teammate_get_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For teammate_get_status, this is the rule to start with:
teammate_get_status 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 Ruflo, apply this rule, and every teammate_get_status call is checked against it from then on.
Questions about teammate_get_status
Get team and teammate status. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for teammate_get_status: 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 Ruflo. Nothing to install.
teammate_get_status 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 teammate_get_status 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 teammate_get_status. 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.
teammate_get_status is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue