collaborator_get_collaborator_reviews

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 70 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/collaborator-get-collaborator-reviews.md

WHAT IT DOES

What collaborator_get_collaborator_reviews does on SmartBear MCP

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

Parameter	Type	Required	Description
`role`	string	—	Role to filter reviews (e.g., AUTHOR).
`login`	string	—	Collaborator username to filter reviews.
`toDate`	string	—	Maximal creation date in format "yyyy-MM-dd"
`creator`	boolean	—	Whether to filter by creator.
`fromDate`	string	—	Minimal creation date in format "yyyy-MM-dd"
`fullInfo`	boolean	—	Whether to retrieve full review info.
`reviewPhase`	string	—	Review phase to filter (e.g., PLANNING).

Parameters from the server's own tool schema.

RISK

Why collaborator_get_collaborator_reviews is rated Low

This tool performs a straightforward data retrieval operation with filtering options. There are no side effects, no data modification, deletion, or code execution. The parameters only control what existing data is returned, not whether any changes occur.

From the tool's definition The tool description explicitly states it 'Retrieves reviews from Collaborator using ReviewService.getReviews.' All parameters are filter/query parameters (login, role, creator, reviewPhase, fullInfo, fromDate, toDate) with no write, delete, or execution…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs collaborator_get_collaborator_reviews safely

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

collaborator_get_collaborator_reviews Allowed

collaborator_get_collaborator_reviews 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": {
    "collaborator_get_collaborator_reviews": {}
  }
}

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

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

FAQ

Questions about collaborator_get_collaborator_reviews

What does the collaborator_get_collaborator_reviews tool do? +

Retrieves reviews from Collaborator using ReviewService.getReviews. All parameters are optional and only provided ones are sent. Parameters: - login (string): Collaborator username to filter reviews. - role (string): Role to filter reviews (e.g., AUTHOR). - creator (boolean): Whether to filter by creator. - reviewPhase (string): Review phase to filter (e.g., PLANNING). - fullInfo (boolean): Whether to retrieve full review info. - fromDate (string): Minimal creation date in format "yyyy-MM-dd" - toDate (string): Maximal creation date in format "yyyy-MM-dd". It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does collaborator_get_collaborator_reviews accept? +

collaborator_get_collaborator_reviews accepts 7 parameters: role, login, toDate, creator, fromDate, fullInfo, reviewPhase. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on collaborator_get_collaborator_reviews? +

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

What risk level is collaborator_get_collaborator_reviews? +

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

Can I rate-limit collaborator_get_collaborator_reviews? +

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

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

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

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear 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 →