get_screener_fields

Get available screener field metadata. Returns field names, data types, descriptions,

Server Signal8 MCP Server signal8ai/signal8-mcp
Category Read
Risk class Low
Parameters 00 required

What get_screener_fields does on Signal8 MCP Server

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

Why get_screener_fields needs a policy

This tool retrieves metadata about available fields in a financial screener—it queries structural information rather than executing code, modifying data, or accessing sensitive financial records. Even in the context of a financial research platform, metadata enumeration is a read-only operation with minimal blast radius if misused by an agent. It cannot move money, delete data, or trigger external operations.

From the tool's definition Tool name 'get_screener_fields' and description 'Get available screener field metadata. Returns field names, data types, descriptions' indicate a retrieval operation that returns schema/metadata information with no side effects.

Questions about get_screener_fields

What does the get_screener_fields tool do? +

Get available screener field metadata. Returns field names, data types, descriptions,. It is categorised as a Read tool in the Signal8 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_screener_fields? +

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

What risk level is get_screener_fields? +

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

Can I rate-limit get_screener_fields? +

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

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

get_screener_fields is provided by the Signal8 MCP Server MCP server (signal8ai/signal8-mcp). 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.