No, there is no policy for this. You could perhaps figure out a way, e.g. via Group Policy somehow, to set this value to 100...
...but that doesn't really solve the problem, and will affect all environments they connect to, including their local instance(s).
You can prevent
SELECT * by adding this computed column to the table (or to a view that references the table):
ALTER TABLE dbo.whatever ADD [No Select Star!] AS (CONVERT(INT,1/0));
But again, that doesn't prevent them from selecting all rows. I have to agree with Thomas here - why are these developers allowed to run whatever ad hoc queries they feel like against critical systems? Do you really want them to even be able to do this:
SELECT TOP (100) * FROM dbo.BigTable, dbo.BigTable AS b ORDER BY NEWID();
(Go ahead, try it - even a query that is somehow artificially limited to return 100 rows can bring your system to its knees.)
What you could do is deny them direct access to the tables, and force their access through stored procedures - which take parameters for row counts etc., and the code could cap how high those could go (either by checking or using a parameter of type