microservice_detect

Analyze a repo for Yaver-wrappable microservices: long-running workers, serverless cron endpoints, and companion services. Read-only; returns proposed yaver.companion.yaml.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/microservice-detect.md

WHAT IT DOES

What microservice_detect does on Yaver

AI agents call microservice_detect to retrieve information from Yaver 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
`repo`	string	—	Project/repo directory. Defaults to the MCP session working directory.
`project`	string	—	Optional Yaver companion project slug.

Parameters from the server's own tool schema.

RISK

Why microservice_detect is rated Low

Tool only analyzes and returns configuration suggestions without modifying system state or triggering operations.

From the tool's definition Analyze a repo...returns proposed yaver.companion.yaml. Read-only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs microservice_detect safely

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

microservice_detect Allowed

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

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

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

FAQ

Questions about microservice_detect

What does the microservice_detect tool do? +

Analyze a repo for Yaver-wrappable microservices: long-running workers, serverless cron endpoints, and companion services. Read-only; returns proposed yaver.companion.yaml. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does microservice_detect accept? +

microservice_detect accepts 2 parameters: repo, project. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on microservice_detect? +

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

What risk level is microservice_detect? +

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

Can I rate-limit microservice_detect? +

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

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

microservice_detect is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →